From: Chris W. <ch...@cw...> - 2003-12-11 08:33:21
|
* Vsevolod (Simon) Ilyushchenko (si...@cs...) [031210 16:57]: > I may have gotten lazy, but here is a feature that could be useful. If a > certain field is not set in the object, the SQL statements that are > generated to insert or update values do not contain *any* value for that > field. Thus, they are syntactically invalid: > > update table set field1 = value1, field2 = , field3 = value3, ... Oh, that's clearly wrong. > Obviously, I can work around this in the application code, but it would > be really cool if for fields that can be NULL SPOPS would automatically > put NULL into the SQL code if the value is not defined. No, you shouldn't have to work around this. I'll look into it. One note on this: the 'skip_undef' feature may help, since it will not include ANY fields in an insert or update that are undefined. Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988 |