On Fri, Aug 24, 2012 at 12:45 AM, Pavel Ivanov wrote:
> This is a documented change. See http://www.sqlite.org/releaselog/3_7_11.html:
>
> "Pending statements no longer block ROLLBACK. Instead, the pending
> statement will return SQLITE_ABORT upon next access after the
> ROLLBACK."
>
> There was e
This is a documented change. See http://www.sqlite.org/releaselog/3_7_11.html:
"Pending statements no longer block ROLLBACK. Instead, the pending
statement will return SQLITE_ABORT upon next access after the
ROLLBACK."
There was even some explanation of reasons for that somewhere on the list.
P
Consider the following operations (full test program attached):
stmt <- prepare conn "SELECT * FROM foo"
Row <- step stmt
exec conn "BEGIN; ROLLBACK"
Row <- step stmt
Namely, we prepare a statement with sqlite3_prepare_v2, call
sqlite3_step (giving us SQLITE_ROW). While the state
On Tue, Aug 21, 2012 at 8:54 PM, Dwayne Litzenberger wrote:
> Recent versions of SQLite fail to run on Mac OS X 10.4 (Tiger) with
> the following error message:
>
We don't test SQLite in MacOS 10.4, but we do test every release on MacOS
10.2. For that platform, we add the compile-time option:
On Fri, Jun 15, 2012 at 9:22 AM, Luigi wrote:
> CREATE TABLE t1 (A1 INTEGER NOT NULL,A2 INTEGER NOT NULL,A3 INTEGER NOT
> NULL,A4 INTEGER NOT NULL,PRIMARY KEY(A1));
> REPLACE INTO t1 VALUES(1,11,111,);
> REPLACE INTO t1 VALUES(2,22,222,);
> REPLACE INTO t1 VALUES(3,33,333,);
> CREATE
That sets the value of the col1 field in every row in tb1 to the value
retrieved from tb2. I doubt that's what he wants, but he didn't tell us, so
maybe it is.
RobR
-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]
On Behalf Of Igor Tand
On Thu, Aug 23, 2012 at 1:31 AM, Pavel Ivanov wrote:
> > When I implement the same mechanism for saving the
> > memory database back to disk, the size of disk file is 4x of the original
> > disk file size.
>
> What is "original disk file size" here? Is it an empty database,
> database with some d
yanhong.ye wrote:
> update tb1 set col1=(select col1 from tb2 ) where tb1.co2=tb2.co2;
The closing parenthesis is in the wrong place:
update tb1 set col1=(select col1 from tb2 where tb1.co2=tb2.co2);
--
Igor Tandetnik
___
sqlite-users mailing list
s
Are you certain there exist rows in tb1 and tb2 that satisfy the condition?
What happens when you try? Is any error message or number returned? Can you
run the same query inside an SQLite management tool like SQLite Spy? Does it
work there? Please provide us ALL of the relevant information
2012/8/23 Simon Slavin :
> I'm trying to log SQL commands which might make changes to the database, but
> not those which just read it...
> Simon.
Use triggers.
--
Kit
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin
I'm trying to log SQL commands which might make changes to the database, but
not those which just read it. This routine does /not/ need to deal with
arbitrary tricksy SQL commands generated by third parties, just SQL commands I
myself have written or my program has generated, intended specifica
update tb1 set col1=(select col1 from tb2 ) where tb1.co2=tb2.co2;
it couldn't work
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
12 matches
Mail list logo