Re: [sqlite] upstreaming Chromium patches for file handle passing support

On Fri, Aug 27, 2010 at 04:58, Richard Hipp wrote: > The VFS interface is published, stable, and documented. I think the VFS is > the interface you should be using. > > You do not have to patch os_unix.c. Leave it unchanged. Sounds good to me. This is one of my goals - to

Re: [sqlite] rollback to savepoint regression / bug with journal_mode=off and locking_mode=exclusive

On 27.08.2010 18:58, Noah Hart wrote: > http://www.sqlite.org/pragma.html#pragma_journal_mode states > > The OFF journaling mode disables the atomic commit and rollback capabilities > of SQLite. The ROLLBACK command no longer works; it behaves in an undefined > way. Applications must avoid using

Re: [sqlite] rollback to savepoint regression / bug with journal_mode=off and locking_mode=exclusive

http://www.sqlite.org/pragma.html#pragma_journal_mode states The OFF journaling mode disables the atomic commit and rollback capabilities of SQLite. The ROLLBACK command no longer works; it behaves in an undefined way. Applications must avoid using the ROLLBACK command when the journal mode is

[sqlite] rollback to savepoint regression / bug with journal_mode=off and locking_mode=exclusive

SQLite 3.7.2 has a regression with journal_mode=off and locking_mode=exclusive. Here is the SQL reproduce: drop table if exists t1; PRAGMA locking_mode=exclusive; pragma locking_mode; CREATE TABLE t1(a PRIMARY KEY, b); PRAGMA journal_mode = off; BEGIN; INSERT INTO t1 VALUES(13,

Re: [sqlite] SQLite version 3.7.2

The problem is in Apple-contributed code to work with their NFS filesystem. You can disable all of the Apple code by compiling with -DSQLITE_ENABLE_LOCKING_STYLE=0 On Fri, Aug 27, 2010 at 10:03 AM, Jim Wilcoxson wrote: > Using the SQLite Encryption Edition rev 3.7.0.1, the

Re: [sqlite] SQLite version 3.7.2

Using the SQLite Encryption Edition rev 3.7.0.1, the latest released version, on OSX Tiger (10.4), results in an undefined reference to gethostuuid. Is OSX 10.4 no longer supported? Thanks, Jim -- HashBackup: easy onsite and offsite Unix backup http://sites.google.com/site/hashbackup On Mon,

Re: [sqlite] EXTERNAL: Fwd: Conflicting table existence errors after SAVEPOINT & ROLLBACKs

I confirmed this also is a bug in 3.7.2 Interesting thing thoughif you add one .schema statement the problem goes away. I wanted to see what it thought about the schema along the way. So after With bug: SQLite version 3.7.2 Enter ".help" for instructions Enter SQL statements terminated

[sqlite] Fwd: Conflicting table existence errors after SAVEPOINT & ROLLBACKs

Repost after being bounced - if the moderator hasn't looked at this in 16 days, perhaps he never will... > Your mail to 'sqlite-users' with the subject > >Conflicting table existence errors after SAVEPOINT & ROLLBACKs > > Is being held until the list moderator can review it for approval. > >

Re: [sqlite] SQL script help.

What language are you writing in? Why do you need to know the # of rows? What are you doing with that information? The select itself does stop (obviously). >From a Windows command prompt you can just do this echo SELECT * FROM myTable WHERE _rowid_ >= 100 AND _rowid_ <= 102 | sqlite3

Re: [sqlite] upstreaming Chromium patches for file handle passing support

On Thu, Aug 26, 2010 at 6:02 PM, Paweł Hajdan, Jr. wrote: > Please take a look at chromium_sqlite3 functions in > > http://src.chromium.org/viewvc/chrome/trunk/src/third_party/sqlite/src/src/os_unix.c?view=markup > > They are needed because in Chrome the browser process

Re: [sqlite] SQL script help.

Kirk, You can use the aggregate function count. So if you have a table called foo, do this, SELECT COUNT(*) FROM foo; That'll give you the number of rows in the table. Denis On Fri, Aug 27, 2010 at 6:30 AM, Paul Corke wrote: > On 26 August 2010 19:02, Kirk

Re: [sqlite] SQL script help.

On 26 August 2010 19:02, Kirk Clemons wrote: > I would like to be able to create an output log of each row. But I > need to know how many rows there are in the database unless there is > a way to tell sqlite to stop at the end? Do you just want: SELECT * FROM myTable which will return every

Re: [sqlite] SQL script help.

I would like to be able to create an output log of each row. But I need to know how many rows there are in the database unless there is a way to tell sqlite to stop at the end? -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf

Re: [sqlite] SQL script help.

Thank you, So how do I get the total count of rows? -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Simon Slavin Sent: Thursday, August 26, 2010 8:59 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] SQL