[sqlite] Exitcode and savepoint problems during archiving

Hello, I have discovered three potential bugs in sqlite which I think are somewhat related. The first one is: when I run the following command and immediately CTRL-C on it in a shell, I get: $ sqlite3 -cmd ".trace TRACE" db.sqlite -Ac /usr ; echo $? ^CERROR: interrupted ERROR: no

Re: [sqlite] SQLite 3.24.0 regression from enhanced "ALTER TABLE true/false DEFAULT" on TEXT field

Thanks ! -- Sent from: http://sqlite.1065341.n5.nabble.com/ ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite 3.24.0 regression from enhanced "ALTER TABLE true/false DEFAULT" on TEXT field

On January 11, 2019 7:03:03 AM EST, Christian Nols wrote: >From "Enhance ALTER >TABLE so that it >recognizes "true" and "false" as valid arguments to DEFAULT" introduced >in 3.24.0 > >A TEXT field can no longer have "true"/"false" default values.

Re: [sqlite] [EXTERNAL] SQLite 3.24.0 regression from enhanced "ALTER TABLE true/false DEFAULT" on TEXT field

Please retry with correct string quoting, i.e. single quotes. Double quotes are reserved for identifiers and interpreted as strings only if there is no such identifier. "false" (double quotes) is an identifier, 'false' (single quotes) is a string. -Ursprüngliche Nachricht- Von: sqlite-u

[sqlite] SQLite 3.24.0 regression from enhanced "ALTER TABLE true/false DEFAULT" on TEXT field

From "Enhance ALTER TABLE so that it recognizes "true" and "false" as valid arguments to DEFAULT" introduced in 3.24.0 A TEXT field can no longer have "true"/"false" default values. The smart DEFAULT conversion should not be triggered if the hin