Jay A. Kreibich wrote: > > That, or something like sqlite3_clear_bindings() that actually > *clears* the bindings (e.g. whatever state they are in just after a > prepare), and not just sets them to an explicit NULL, as the current > function does. >
Jay, That wouldn't help. The default value is *only* used when no value is provided by the insert statement. If the insert statement has a parameter that can be bound, it is supplying a non-default value, and that value will be used instead of the default value. You really do need different statements, with and without a value for the column that is to get the default value. Dennis Cote _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
