On 7/23/07, Oleg Broytmann <[EMAIL PROTECTED]> wrote: > I'd like to lift the restriction and allow NULLs in alternateID columns. > Any idea, pro or contra suggestion?
I'd agree with Ian that something which can be NULL doesn't really follow the semantics of an ID field. With an ID field I would expected something like: x = obj.SOME_ID assert(obj == get_obj_by_id(x)) to always hold. This wouldn't be true if the ID was allowed to be NULL. Perhaps some way of accessing objects using a unique field would be better? Sort of like a generic version of Ian's solution but automatically added for fields declared unique. Schiavo Simon ------------------------------------------------------------------------- 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/ _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
