Re: [sqlite] Not Null Constraint Issue?

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

[sqlite] Bad database manager. No biscuit.

tl;dr: CSV is a useful standard which, like most things in computing, has a couple of 'gotchas'. Not all '.CSV' files are CSV files. Can't give details but I just identified a problem which had caused the SQL database owner £100,000 == US$130,000 == €117,000 of damage, mostly because

Re: [sqlite] Not Null Constraint Issue?

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. This makes me feel a bit better, as now we have a reason for the constraint not triggering. INTEGER objects within

[sqlite] Problem with page cache

The pcache1FetchStage2 function has "*(void **)pPage->page.pExtra = 0;" although this does not seem to be documented, nor is there an assertion in pcache1.c (although in pcache.c there is). Perhaps the documentation should be corrected. ___

[sqlite] SQLite 3.31.0 enters pre-release testing

Our intent is that there will be no more changes to SQLite, other than documentation updates and bug fixes, prior to the 3.31.0 release. Consider the "Prerelease Snapshot" at https://sqlite.org/download.html to be a beta-release. Please test that snapshot and report any problems. A terse summary

Re: [sqlite] sqlite3_limit equivalent in System.Data.SQLite.dll

That would be great. Thanks! Do you have an estimated time for this release? Keith -Original Message- From: sqlite-users On Behalf Of Joe Mistachkin Sent: Thursday, January 16, 2020 2:37 PM To: SQLite mailing list Subject: Re: [sqlite] sqlite3_limit equivalent in

[sqlite] Truncation/rounding error in strftime(x, 'unixepoch')

Hi, some time ago there was an error reported when running the testsuite on ix86, in the date.test/date-2.2c-*. The error happens as a string like 1237962480.003 gets parsed and rounded to 1237962480.002999... and is later truncated to 1237962480.002. The rounding error happend in

Re: [sqlite] SQLite 3.31.0 enters pre-release testing

Richard Hipp, on Friday, January 17, 2020 07:56 AM, wrote... > A terse summary of changes can be seen at > https://www.sqlite.org/draft/releaselog/current.html No gain in speed? :-) I love it when I see, "2% faster..." Thanks. josé ___ sqlite-users