On Sep 6, 2007, at 7:16 PM, John Siracusa wrote: > Or I suppose you could do the reverse, requiring a "special" value to > trigger the use of a default and leaving undef as the null stand-in.
That'd by far be my preference. In the application code undef and NULL maps so beautifully. Also it keeps use of the "special" value mostly inside RDBO. > I don't like any of those choices: too much trouble in the common > case to > enable what I imagine is a rare case (yours, unfortunately). Any > other > solutions? We've already run into it twice. :-) And it seems like something that'll keep creeping through the abstraction... It basically makes NULL columns impossible to use, I think that's worth a little trouble to correct. - ask -- http://develooper.com/ - http://askask.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
