On 6/26/17, 11:15 AM, "[email protected] on behalf of Richard Hipp" <[email protected] on behalf of [email protected]> wrote: > If you get the latest check-in (https://www.sqlite.org/src/info/trunk) there > is a new option on the "sqlite3" command called "-unsetnull 1" which causes > "db eval" to work as you desire - by unsetting the array elements for NULL > values. This option is off by default for legacy compatibility.
Could that be an option on the eval command rather than the db, so that packages can safely use the feature on databases they don’t “own”? _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
