[sqlite] autoincrement and fts2?

Is there any way to use a INTEGER PRIMARY KEY AUTOINCREMENT on a table that has FTS2? Specifying it in the obvious manner looks like it works, but the column just ends up with nulls in it. - a -- PGP/GPG: 5C9F F366 C9CF 2145 E770 B1B8 EFB1 462D A146 C380

[sqlite] Re: autoincrement and fts2?

"Scott Hess" <[EMAIL PROTECTED]> writes: > In fts tables all columns other than rowid are of type TEXT. It > doesn't matter what you put in the type, they will be of type TEXT. > The rowid is the standard SQLite rowid, so it does provide an INTEGER > PRIMARY KEY AUTOINCREMENT column. Scott,

[sqlite] Re: autoincrement and fts2?

>> > In fts tables all columns other than rowid are of type TEXT. It >> > doesn't matter what you put in the type, they will be of type TEXT. >> > The rowid is the standard SQLite rowid, so it does provide an INTEGER >> > PRIMARY KEY AUTOINCREMENT column. >> Scott, thanks for your reply.

[sqlite] why doesn't this work? (fts rowids)

Hello, I need to create a perpetually-unique column in an FTS2 table. For example: create virtual table t using fts2(c); insert into t (c) values ('a'); select rowid,c from t; 1|a delete from t; insert into t (c) values ('b'); select rowid,c from t; 1|b How can I get the last

[sqlite] any way to SELECT the 100th-104th row of a table?

Hello. This is probably a stupid question, but... Is there any way to include some phrase in a SELECT clause that will match only the Nth-Mth rows of a table, for some values of N and M? Note that ROWID isn't what I'm looking for -- if you delete rows from a table the ROWID no longer matches

[sqlite] test post via gmane

Hopefully now that sqlite-users is on mailman it will take posts sent via gmane. If this message shows up, then that is the case. - a ___ sqlite-users mailing list sqlite-users@sqlite.org

[sqlite] sqlite using whole-file (not byte-range) locking

I'm interested in using SQLite with AFS (the Andrew FileSystem). Unlike NFS, AFS has solid, reliable support for *whole-file* advisory locking across the network. AFS does some very sophisticated caching, so an SQLite database in AFS accessed by a single reader/writer would be very efficient. A

[sqlite] Re: sqlite using whole-file (not byte-range) locking

[EMAIL PROTECTED] writes: > In the latest versions of SQLite (3.3.0 and later) you can provide > SQLite with customized locking code at run-time. So you can > easily add AFS support that uses whole-file locking instead of > the goofy byte-range stuff I have to do for Win95. That's fantastic.

[sqlite] detect afs, --enable-locking-style, non-darwin fs detection

AFS (the Andrew FileSystem) supports whole-file locks but not byte-range locks. Unfortunately, it has a problematic "feature" whereby it will claim to grant requests for byte-range locks, but not actually perform any locking activity. This unfortunately can easily lead to corruption for

[sqlite] [updated] detect afs, --enable-locking-style, non-darwin fs detection

In addition to the functionality in the previous patch, this patch includes a new function testProcessLockingBehavior(), which is conceptually similar to testThreadLockingBehavior but using fork() instead of pthread_create(). This might sound obvious: lock the first byte of a file, fork() a

[sqlite] Re: [updated] detect afs, --enable-locking-style, non-darwin fs detection

t act of relinquishment in perpetuity of all present and future rights this code under copyright law." I have mailed off the copyright release. - a Adam Megacz <[EMAIL PROTECTED]> writes: > In addition to the functionality in the previous patch, this patch > i

[sqlite] FTS1 dump/restore needs column names

It seems that when doing a dump/restore on databases with FTS1 enabled, the INSERT commands in the dump need column names. That is, if the dump looks like this: INSERT INTO "foo" VALUES (x,y,z) You get the error SQL error: table foo has 4 columns but 3 values were supplied Apparently if

[sqlite] Re: developers mailing list, ignored patches

The following message is a courtesy copy of an article that has been posted to gmane.comp.db.sqlite.general as well. [EMAIL PROTECTED] writes: > It is true that I do not use autoconf much. But I do use it now > and then. The main problem is that autoconf is broken on my > SuSE 10.1

[sqlite] garbage between end of SQL and COMMIT in a dump?

The following message is a courtesy copy of an article that has been posted to gmane.comp.db.sqlite.general as well. Using sqlite 3.3.10 I'm experiencing a strange situation where .dump appears to repeat the last few lines of the dump (not including the final "COMMIT") twice. Has anybody else

[sqlite] Re: developers mailing list, ignored patches

[EMAIL PROTECTED] writes: >> I also printed out and signed the copyright papers and mailed them in. > Your copyright release and your patches arrived in today's post. > The postmark is smeared somewhat but it does appear to say > "2? DEC 2006" (where the ? is illegible.) > So from Oakland,

[sqlite] how do I know for sure that my data hit the disk?

>From http://www.sqlite.org/lockingv3.html If multiple commands are being executed against the same SQLite database connection at the same time, the autocommit is deferred until the very last command completes. For example, if a SELECT statement is being executed, the execution of the

Re: [sqlite] how do I know for sure that my data hit the disk?

"Igor Tandetnik" <[EMAIL PROTECTED]> writes: >> I have an application that absolutely must not return from a certain >> call until the results of an update are safely committed to disk. > Open a separate connection to the same database, perform the update on > this connection. I am in an

Re: [sqlite] how do I know for sure that my data hit the disk?

"Igor Tandetnik" <[EMAIL PROTECTED]> writes: >>> Open a separate connection to the same database, perform the update >>> on this connection. My understanding is that this second connection will block and then time out if the first connection has a read operation in progress, so I don't think

Re: [sqlite] SQLite JDBC driver performance

Christopher Mason writes: > [Apologies for posting this here, but the sqlitejdbc list appears to be > defunct.] Google deleted it without warning or explanation: http://www.zentus.com/sqlitejdbc/google-group-disappearance.html It has been relocated