On 7/21/06, Ask Bjørn Hansen <[EMAIL PROTECTED]> wrote: > On Jul 21, 2006, at 15:21, John Siracusa wrote: >>> Also, it would be very nice if columns that don't match could cause a fatal >>> error instead of being silently dropped. I will see if I can make a patch >>> for that if you agree. >> >> IIRC, the existing "silent" behavior is actually used by RDBO in some cases, >> but a "mode" where it causes a fatal error could be added (set by a param to >> the call or a class attribute maybe) > > Wouldn't that interfere with how RDBO is using it anyway then? > > How about making the fatal error the default and then have RDBO pass > a "drop columns silently" option? > > (I would find the fatal error more helpful)
In SVN, I've made it unconditionally fatal and adjusted RDBO so that all tests pass. The change is documented in QueryBuilder's POD and will go out in the next release. -John ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
