value sitting
in an INTEGER field.
I definitely know to look out for this now.
From: Simon Slavin
To: SQLite mailing list
Subject: Re: [sqlite] Not Null Constraint Issue?
Message-ID: <46053091-b9ab-43c4-b7f9-c89d70986...@bigfraud.org>
Content-Type: text/plain; charset=us-ascii
On
On 17 Jan 2020, at 6:39pm, Justin Gielski 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
ist
> >Subject: Re: [sqlite] sqlite3_limit equivalent in System.Data.SQLite.dll
> >
> >
> >Yes, the NuGet packages are included in the release.
> >
> >Sent from my iPhone
> >
> >> On Oct 24, 2019, at 9:13 AM, Keith Bertram
> >wrote:
> >
On 2020/01/16 12:47 am, Simon Slavin wrote:
On 15 Jan 2020, at 9:44pm, Justin Gielski wrote:
*"database is locked release restore point sqlite"*
If there's nothing in your code that caused that to happen, then I would
suspect a transient hardware glitch. Does your code use SAVEPOINTs ?
On 15 Jan 2020, at 9:44pm, Justin Gielski wrote:
> *"database is locked release restore point sqlite"*
If there's nothing in your code that caused that to happen, then I would
suspect a transient hardware glitch. Does your code use SAVEPOINTs ?
> The database locking mode is set to NORMAL
Good Afternoon
I wanted to pass along a really strange issue we just ran into in with one
of our products. We have a simple table with an INTEGER column set with a
NOT NULL DEFAULT 0 constraint.
We have no clue how it happened, but some how a null value was successfully
inserted into this column
6 matches
Mail list logo
