Hello Pavel,
* 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 data, database with exactly the same data you
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
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
2012/8/23 Simon Slavin slav...@bigfraud.org:
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
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
yanhong.ye y...@sohu.com 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
On Tue, Aug 21, 2012 at 8:54 PM, Dwayne Litzenberger dl...@dropbox.comwrote:
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
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 statement
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.
On Fri, Aug 24, 2012 at 12:45 AM, Pavel Ivanov paiva...@gmail.com 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.
10 matches
Mail list logo