as the trigger name.
--
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users On
>Behalf Of John G
>Sent: Saturday, 7 March, 2020 09:49
>To: SQLite mailing list
On 7 Mar 2020, at 4:49pm, John G wrote:
> Would it be possible to create an SQL verification program, which just like
> 'sqlite3_analyzer' and 'sqldiff' could be run separately?
> It could *warn* about apparently incompletely defined triggers and other
> possible pitfalls.
The shell tool has t
Would it be possible to create an SQL verification program, which just like
'sqlite3_analyzer' and 'sqldiff' could be run separately?
It could *warn* about apparently incompletely defined triggers and other
possible pitfalls.
Then developers could use it before installing the next version of SQLit
On 26/02/2020 12:18, Richard Hipp wrote:
On 2/26/20, Jean-Luc Hainaut wrote:
Hi all,
It seems that SQLite (version 31.1) accepts a trigger declaration in
which the name is missing. When fired, this trigger doesn't crashes but
exhibits a strange behaviour. In particular, while expression
"new."
SQLite is even better than I thought...
From: sqlite-users on behalf of
Richard Hipp
Sent: Wednesday, February 26, 2020 11:44 AM
To: SQLite mailing list
Subject: Re: [sqlite] Trigger name missing
On 2/26/20, Simon Slavin wrote:
>
> Backward compati
On 2/26/20, Simon Slavin wrote:
>
> Backward compatibility ? Do you think anyone who used the word AFTER
> really wants a BEFORE trigger ? More likely to be a bug they should know
> about.
We have seen triggers like this in the wild, that work as intended.
If we change it to throw an error, the
On 26 Feb 2020, at 2:15pm, Dan Kennedy wrote:
> A statement like the following creates a "BEFORE" trigger named "AFTER". Does
> that explain things?
>
> CREATE TRIGGER AFTER INSERT ON t1 BEGIN
> ...
> END;
>
> I find I fall into this trap about once every 18 months...
If only you knew
On 26/2/63 16:31, Jean-Luc Hainaut wrote:
Hi all,
It seems that SQLite (version 31.1) accepts a trigger declaration in
which the name is missing. When fired, this trigger doesn't crashes
but exhibits a strange behaviour. In particular, while expression
"new." in an "insert" trigger returns t
On 2/26/20, Jean-Luc Hainaut wrote:
> Hi all,
>
> It seems that SQLite (version 31.1) accepts a trigger declaration in
> which the name is missing. When fired, this trigger doesn't crashes but
> exhibits a strange behaviour. In particular, while expression
> "new." in an "insert" trigger returns t
Hi all,
It seems that SQLite (version 31.1) accepts a trigger declaration in
which the name is missing. When fired, this trigger doesn't crashes but
exhibits a strange behaviour. In particular, while expression
"new." in an "insert" trigger returns the correct value, the
equivalent expression
10 matches
Mail list logo