On Dec 12, 2007 8:34 AM, Ted Zlatanov <[EMAIL PROTECTED]> wrote: > On Tue, 11 Dec 2007 12:10:00 -0500 "John Siracusa" <[EMAIL PROTECTED]> wrote: > JS> The undef_sets_null feature that alters the behavior of default > JS> columns values will almost certainly go out in the next release (which > JS> is coming soon). It may or may not be public (depending on if I have > JS> time to do docs and add support for it to the rest of the column > JS> types), but the code will be there. I still think the name is kind of > JS> lame, however, and I'm open to suggestions. > > (some are inverted) > > undef_is_null > undef_as_null > undef_eq_null
Undef is always treated as null. The distinction in this case is that explicitly setting the column to undef overrides the default value. > explicit_null That's closer, but it feels like even less of a complete description than undef_sets_null. -John ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
