On 17 Jan 2020, at 6:39pm, Justin Gielski <justin.giel...@gmail.com> wrote:
> After looking into the issue a bit more, it appears the INTEGER value was > actually saved into the DB as an EMPTY not a NULL, which is currently allowed > by the database constraints. Could you show us the constraint you feel disallows those things ? We might be able to find a loophole in the exact way you phrased it. Also, could someone explain to me what EMPTY means here ? I've seen '' called "empty string" but it doesn't seem to be normal SQL language. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
