Re: [sqlite] sqlite-3.31.0 segfaults on fuzzcheck on s390x architectures

On Mittwoch, 29. Januar 2020 13:40:44 CET Richard Hipp wrote: > Please retry using this check-in: > https://www.sqlite.org/src/info/b20503aaf5b6595a The failings test now pass on all architectures: - ix86/x86_64 - armv7hl, aarch64 - ppc32be, ppc64be, ppc64le - s390x Kind regards, Stefan > On

Re: [sqlite] IO Short Read Error when inserting a TEXT column

On 1/28/20, rgarnett wrote: > the step function fails > with an IO Error Short Read.The VFS I am using I developed myself from the > demo on the sqLite website. I suspect there may be problems with this code I suspect you are correct. The SQLITE_IOERR_SHORT_READ is an error code that is only

Re: [sqlite] Virtual table OR constraint bug

Hi folks, Just wanted to check up on this to see if this issue is something which is being tracked and if there was a potential fix in the works? Thanks, Lalit On Thu, 2 Jan 2020 at 15:13, Lalit Maganti wrote: > Hi all, > > I believe that I have found a bug in the virtual table bytecode

Re: [sqlite] Virtual table OR constraint bug

On 29/1/63 20:09, Lalit Maganti wrote: Hi folks, Just wanted to check up on this to see if this issue is something which is being tracked and if there was a potential fix in the works? Thanks for the excellent bug report and minimal reproduction case. Now fixed here:  

[sqlite] single table data collapse with constraints

Hi, I am emailing to ask if someone could advise me how to create a query or queries which will collapse some data based on a limited number of constraints. I am currently attempting to complete this task using DB Browser for SQLite. I have tried to write a WITH RECLUSIVE statement as I think

Re: [sqlite] Virtual table OR constraint bug

Thank you for the fast fix! Best, Lalit On Wed, 29 Jan 2020 at 15:07, Dan Kennedy wrote: > > On 29/1/63 20:09, Lalit Maganti wrote: > > Hi folks, > > > > Just wanted to check up on this to see if this issue is something which > is > > being tracked and if there was a potential fix in the

Re: [sqlite] Generated columns and COLLATE in the AS parens

On 1/29/20, Markus Winand wrote: > Hi! > > I think there might be a glitch in the way SQLite 3.31.x derives the > collation information from the expression of a generated column. I think the current behavior is correct. If you want a column to have a non-standard collating sequence, you should

Re: [sqlite] sqlite-3.31.0 segfaults on fuzzcheck on s390x architectures

Please retry using this check-in: https://www.sqlite.org/src/info/b20503aaf5b6595a On 1/28/20, Brüns, Stefan wrote: > On Dienstag, 28. Januar 2020 18:26:05 CET Brüns, Stefan wrote: >> On Dienstag, 28. Januar 2020 16:16:01 CET Richard Hipp wrote: >> > On 1/27/20, Ondrej Dubaj wrote: >> > > Hi,

Re: [sqlite] Is sqlite3 smart enough to remove redundant command?

It's going to run both since you asked it to. Even if it was in a compiled language where the compiler could look ahead and was looking to implement that sort of optimization, then for example there still might be triggers on the table which would need to be run, or other constraints on the

Re: [sqlite] Is mutliple-execute-one-commit slower than multiple single-execute-single-commit?

On 1/29/20 1:42 AM, Peng Yu wrote: Hi, I have two python programs using sqlite3. They function the same, except the following. In the first, execute() is called in batches and then commit() is called following them. In the second, commit() is called after each execute(). It seems that the

Re: [sqlite] sqlite-3.31.0 segfaults on fuzzcheck on s390x architectures

On Dienstag, 28. Januar 2020 18:26:05 CET Brüns, Stefan wrote: > > On armv7l, there is another failure in the fuzztests, with and without the > patch: > sessionfuzz-data1.db: sessionfuzz: ./sqlite3.c:57249: pager_open_journal: > Assertion `rc!=SQLITE_OK || isOpen(pPager->jfd)' failed. I had

[sqlite] Generated columns and COLLATE in the AS parens

Hi! I think there might be a glitch in the way SQLite 3.31.x derives the collation information from the expression of a generated column. In particular, COLLATE inside the AS parens seems to be ignored, but it is honoured after the parens: SQLite version 3.31.1 2020-01-27 19:55:54 Enter

Re: [sqlite] New word to replace "serverless"

I would not choose a new wording. "Serverless" is correct, and just because others start using "serverless" in a wrong manner, I don't see any need for a change. Just my 2 cts. - Original Message - From: Richard Hipp To: General Discussion of SQLite Database Sent: Monday, January

Re: [sqlite] single table data collapse with constraints

Excuse the top posting. This perhaps: create table srcdata ( CLS1text not null, CLS2integer not null, START integer not null, END integer not null ); insert into srcdata values ('ABC1',100,0,1); insert into srcdata values ('ABC1',100,1,1); insert into srcdata

[sqlite] Possible caching issue between connections with specific inserts

Hi SQLite development team. I think that I found a bug in SQLite or in System.Data.SQLite and isolated the case when it happens. In short, the newly added row can be missed if it is requested from another connection. The bug is quite stable and can be reproduced on my demo application each

Re: [sqlite] New word to replace "serverless"

"Serverless" has worked flawlessly since inception. Why change now...? The marketing buzzword usage will disappear...long before Dr Hipp convinces the list that email is dead even.  Regards. Brian P Curley On Wed, Jan 29, 2020, 5:39 PM Jim Dodgen wrote: > I vote for ignoring the marketing

Re: [sqlite] New word to replace "serverless"

I vote for ignoring the marketing types and stick with "serverless" Jim "Jed" Dodgen j...@dodgen.us On Wed, Jan 29, 2020 at 10:20 AM Thomas Kurz wrote: > I would not choose a new wording. "Serverless" is correct, and just > because others start using "serverless" in a wrong manner, I don't

Re: [sqlite] Possible caching issue between connections with specific inserts

Alexey Podogov wrote: > > Also, the issue can't be reproduced if: > - Cache size is set to 0; or > - Journal mode is WAL; or > - Password for database is too short (please see examples in the > demo code). > Thanks for the report. I'm looking into it now. -- Joe Mistachkin

[sqlite] Is it necessary to encode() for file names in sqlar format?

I use the following python3 code to create sqlar file. Is it necessary to sys.argv[2].encode('utf-8') in the line of execute()? In other word, does the native sqlar tools inteprete the name column as an encoded value or a non-encode value? Thanks. import sqlite3 conn=sqlite3.connect(sys.argv[1])

[sqlite] Does .commit() ensure the .execute()'s and .executemany()'s called before are run atomically?

In python sqlite3 program, if I call .execute() multiple times then call .commit(). Does it ensure that all the sqlite3 commands specified by execute()'s either all take effect or none effect? In other words, if any error occurs while running the sqlite3 commands specified in execute(), what

Re: [sqlite] Does .commit() ensure the .execute()'s and .executemany()'s called before are run atomically?

On Wednesday, 29 January, 2020 22:45, Peng Yu wrote: >In python sqlite3 program, if I call .execute() multiple times then >call .commit(). Does it ensure that all the sqlite3 commands specified >by execute()'s either all take effect or none effect? Mayhaps yes, mayhaps no. .commit() is merely

Re: [sqlite] Is it necessary to encode() for file names in sqlar format?

sys.argv is a list of unicode text strings. There is no need to specifically encode or decode it so long as sys.getdefaultencoding() returns 'utf-8'. If your version of Python is so old that it returns something else then you need to modify site.py and have it set the default encoding to

Re: [sqlite] Is mutliple-execute-one-commit slower than multiple single-execute-single-commit?

On Tuesday, 28 January, 2020 23:42, Peng Yu wrote: >I have two python programs using sqlite3. They function the same, >except the following. I presume this means you are using the standard (as in included with the standard Python distribution) sqlite3 module? There are other ways to use