|
From: Andrew B. <and...@pu...> - 2004-08-15 00:10:52
|
On Sat, Aug 14, 2004 at 02:51:28PM -0500, Luke Opperman wrote: [...] > > Isn't this a more generic idea, saying "not a required field, and don't > include > when creating"? Ie, a flag that could apply to any Col type, not just > DateTimeCol? Right now, my understanding is that we can have fields that > aren't required for creating SO objects, but SO requires a default > value/function to use in that case and includes it in the INSERT statement. > Not sure what word to use for the flag, "auto" by itself is the right > concept > but pretty generic. "autoInsert"? "databaseDefault"? "defaultFromDatabase"? There's already a "default" flag. When left with its default value (NoDefault), probably SQLObject should just omit it from the INSERT statement, rather than refuse to even try (or perhaps there should be a default=OmitOk or something). Currently, there's no way to make use of a "DEFAULT ..." declaration in a table definition. -Andrew. |
