On 9 Jul 2018, at 4:13pm, Simon Slavin wrote:
> You can find (especially if you're willing to pay) standards for SQL since
> the 1992 one: 1999, 2003, 2006, 2008 etc.. However, they quickly became so
> large and complicated that no implementation of SQL implemented as much of
> the later stan
On 9 Jul 2018, at 1:57pm, Aaron Elkins wrote:
> Thank you for the interesting explanations for SQL specific cases, and I am
> also interested in the SQL standard document after reading your email, can
> you point me to the right place?
SQL-86 was the first widely-adopted SQL standard. Howeve
As far as I know you have to purchase the documents.
- Original Message -
From: Aaron Elkins
To: SQLite mailing list
Sent: Monday, July 9, 2018, 14:57:07
Subject: [sqlite] What happens when a call contains two SQL statement
Hi Ryan,
Thank you for the interesting explanations for SQL
Hi Ryan,
Thank you for the interesting explanations for SQL specific cases, and I am
also interested in the SQL standard document after reading your email, can you
point me to the right place?
Sorry, I did not trust myself to find the official SQL standard by googling.
- Aaron
> On Jul 9,
I see Gunter already answered this for the specific case, I'll just add
some simple rules of thumb for transactions in general:
1. SQLite automagically starts a transaction ONLY when faced with a
single statement. The second statement in your query/list/script is in
its own transaction and not
I am working with Tcl. The best is of-course a general answer, but if it is
depending on the used language I will be satisfied with the Tcl answer. ;-)
Say I have the following code:
set SQLCmd "
DELETE FROM testing
WHERE key = 12
;
INSERT INTO testing
6 matches
Mail list logo
