Re: [sqlite] SQLite Wrapper

2010-04-13 Thread Jay A. Kreibich
On Wed, Apr 14, 2010 at 10:47:48AM +0530, Navaneeth Sen B scratched on the wall: > Hi all, > > I would like to know if a java wrapper is available for SQlite3 APIs. Yes: http://www.sqlite.org/cvstrac/wiki?p=SqliteWrappers -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Our oppone

[sqlite] SQLite Wrapper

2010-04-13 Thread Navaneeth Sen B
Hi all, I would like to know if a java wrapper is available for SQlite3 APIs. Regards, Sen * * ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Index not used in simple look-up-value query

2010-04-13 Thread Diego.Diaz
Thanks Dan for clarifying that NotExists op does a seek on the IPK column. However, I'm still confused as why the first query (simple) takes much longer (from 2 to 5 times more) than the complicated one. Some numbers: 50K runs of the simple query takes ~3 sec in total. 50K runs of the complicate

Re: [sqlite] Index not used in simple look-up-value query

2010-04-13 Thread Dan Kennedy
On Apr 14, 2010, at 1:05 AM, wrote: > Hello, > > I have a question regarding the query-optimizer. I've tested SQLite > with the following situation: > > 1 table defined as > > CREATE TABLE MyTable (ElementID INTEGER CONSTRAINT ElementID_PK > PRIMARY KEY AUTOINCREMENT, Label VARCHAR(255)) > >

[sqlite] Index not used in simple look-up-value query

2010-04-13 Thread Diego.Diaz
Hello, I have a question regarding the query-optimizer. I've tested SQLite with the following situation: 1 table defined as CREATE TABLE MyTable (ElementID INTEGER CONSTRAINT ElementID_PK PRIMARY KEY AUTOINCREMENT, Label VARCHAR(255)) After filling that table with lots of records (e.g. 100K),

Re: [sqlite] SIGSEGV on INSERT DEFAULT VALUES with triggers

2010-04-13 Thread Shane Harrelson
On Tue, Apr 13, 2010 at 12:30 PM, Tomasz Ł. Nowak < tomasz.no...@man.poznan.pl> wrote: > Shane, you wrote: > > I could not reproduce this on the current or 3.6.23 build: > > > > >./sqlite3 -version > > 3.6.23 > > > > >cat script.sql > > CREATE TABLE current(x,y,z); > > INSERT INTO current DEFAULT

Re: [sqlite] SIGSEGV on INSERT DEFAULT VALUES with triggers

2010-04-13 Thread Tomasz Ł . Nowak
Shane, you wrote: > I could not reproduce this on the current or 3.6.23 build: > > >./sqlite3 -version > 3.6.23 > > >cat script.sql > CREATE TABLE current(x,y,z); > INSERT INTO current DEFAULT VALUES ('a', 'b', 30); > > >./sqlite3 -init script.sql > -- Loading resources from script.sql > Error:

[sqlite] SQLite fts3: search for a string in a column

2010-04-13 Thread Manoj M
Is there any way to search for a particular string in a column? I want to search like SELECT * from email_fts WHERE email_fts MATCH 'to:"a...@b.com" OR from:"c...@d.com"' sqlite> .schema email_fts CREATE VIRTUAL TABLE [email_fts] USING fts3 ( [from], [subject], [body], [to], [cc], [filename] R

Re: [sqlite] why block at sqlite3_prepare_v2(*)?

2010-04-13 Thread Pavel Ivanov
To prepare a statement SQLite needs to read the information about schema of your database. So it should inevitably obtain a SHARED lock on the database while doing so. If you have another process having EXCLUSIVE or PENDING on the database then SQLite cannot read schema information and cannot finis

[sqlite] why block at sqlite3_prepare_v2(*)?

2010-04-13 Thread liubin liu
my program is blocked at the point of sqlite3_prepare_v2(*). Why? 512 513 sqlite3_stmt *p_stmt = NULL; 514 printf (" ### 500, %p, %s, %p\n", g_db_base, sql, p_stmt); 515 ret = sqlite3_prepare_v2 (g_db_base, sql, -1, &p_stmt, NULL); 516 printf ("

[sqlite] why block at sqlite3_prepare_v2(*)?

2010-04-13 Thread liubin liu
my program is blocked at the point of sqlite3_prepare_v2(*). Why? 512 513 sqlite3_stmt *p_stmt = NULL; 514 printf (" ### 500, %p, %s, %p\n", g_db_base, sql, p_stmt); 515 ret = sqlite3_prepare_v2 (g_db_base, sql, -1, &p_stmt, NULL); 516 printf (" ##