On Jun 28, 2017 6:51 AM, "Simon Slavin" <[email protected]> wrote:
On 28 Jun 2017, at 9:45am, Clemens Ladisch <[email protected]> wrote: > An explicit NULL works only for the autoincrement column, but not for default values. Really ? In that case I withdraw my previous answer. I thought that NULLs were converted to the default value for a column (which is usually NULL but can be overridden with a DEFAULT clause). Thanks for the correction. Depending on needs, one can make a column not null with on conflict replace, at which point trying to insert or update with null will use the default, but that is only available if your column can never be null. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
