Re: [sqlite] [EXTERNAL] Distinguish type of statements

Thanks! Indeed I was already aware of the `sqlite3_stmt_readonly()` function. But it is not enough in my case. I really need to distinguish between UPDATE, DELETE and INSERT Cheers, Simone -- Sent from: http://sqlite.1065341.n5.nabble.com/ ___

Re: [sqlite] proposal: make the archive option -Au to update only newer files. /Patch included/

On Wed, Mar 20, 2019 at 5:13 PM Захар Малиновский < zakhar.malinovs...@gmail.com> wrote: > Here I include patch file with the changes: fossil diff --from trunk .\src\ > shell.c.in > patch-updateOnlyNewer.patch > (see patch file patch-updateOnlyNewer.patch) > Copy/paste it inline to your message.

[sqlite] proposal: make the archive option -Au to update only newer files. /Patch included/

Hello. I found that the -Au option of the sqlar archive mode always updates files in archive. Currently the command ./sqlite3.exe ./testdb.db -AvuC d:/Go GOPATH takes too much time trying to update every file in archive db, even if they are uptodate. With this proposal updating sqlar archive with

[sqlite] MAX_PATHNAME is too short

Hi. Although SQLite does not have any limits for filenames, there is a limit of 512 characters for the pathname, which seems like an arbitrary choice, as it does not match the limits of any of the filesystem listed in https://en.wikipedia.org/wiki/Comparison_of_file_systems#Limits. In addition

Re: [sqlite] bug report: UPSERT / INSERT ON CONFLICT PK Autoincrement

Stanislav Zabka wrote: > When conflict occurs, no import performs, but PK is incremented nevertheless. says: | Note that "monotonically increasing" does not imply that the ROWID | always increases by exactly one. One is the usual increment. However, | if an

[sqlite] bug report: UPSERT / INSERT ON CONFLICT PK Autoincrement

UPSERT / INSERT ON CONFLICT PK Autoincrement When conflict occurs, no import performs ( as expected ), but PK is incremented nevertheless. example (focus on sqlite_sequence.seq) : run1: initial values - all ok run2: all conflict; no insert (ok) - but sqlite_sequence.seq incremented ( I would

[sqlite] Shell usage/help text inconsistencies

Hello, In the string zOptions in shell.c.in there are a couple of inconsistencies in the usage/help text: " -lookaside SIZE Nuse N entries of SZ bytes for lookaside memory\n" and " -pagecache SIZE Nuse N slots of SZ bytes each for page cache memory\n" where the option definition

Re: [sqlite] INSERTing from another table data

On 20 Mar 2019, at 00:35, Simon Davies wrote: > On Tue, 19 Mar 2019 at 15:07, Tim Streater wrote: >> >> My use case is a mixture of these. My need is to copy a row from a table in >> one db (db1) to a table with identical schema in another db (db2). The >> complication is that there is an id

Re: [sqlite] [EXTERNAL] Distinguish type of statements

Apart from the already mentioned authorizer callbakc , there is the sqlite3_stmt_readonly() function. see https://sqlite.org/c3ref/stmt_readonly.html -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von siscia Gesendet:

Re: [sqlite] .import fails CHECK constraint on valid data

> > For good or bad, check constraints appear to be evaluated before this > conversion. I call that very bad. On Wed, Mar 20, 2019 at 7:58 AM Shawn Wagner wrote: > A manual INSERT demonstrates the same behavior, actually. Using your Tc > table: > > sqlite> insert into Tc values ('12'); >