Re: [sqlite] create table error

close it. that is for my reason. the relloc memory error! "Mohd Radzi Ibrahim" <[EMAIL PROTECTED]> 2007-05-10 16:44 Please respond to sqlite-users@sqlite.org To cc Subject Re: [sqlite] create table error Could it be that the data where *sql is pointing to is being re-used somewhere?

Re: [sqlite] porting sqlite3 to embeded os-----lock question

thank you for your reply. I have make it run on our embeded os and make some simple tests. it runs ok. great!! "Nuno Lucas" <[EMAIL PROTECTED]> 2007-05-12 07:03 Please respond to sqlite-users@sqlite.org To sqlite-users@sqlite.org cc Subject Re: [sqlite] porting sqlite3 to embeded os-l

[sqlite] Re: Limit selection by rolling sum?

Steve Krulewitz <[EMAIL PROTECTED]> wrote: I have a table that I would like to select the first N records where the rolling sum of a given column is less than some literal value. SQL for this might look like: select item_id from items where rolling_sum(item_size) < 1 order by item_name; Is

RE: [sqlite] Limit selection by rolling sum?

filter on a nested select. select id, ( select sum(i2.size) from items i2 where i2.id <= i1.id ) sum_size from items i1 where sum_size < 5; I'm sure performance sucks :-) Something like this would be much faster to do in a pro

[sqlite] replace function?

I get an error in version 3.3.7 when using the replace function as defined here: http://sqlite.org/lang_expr.html "replace(X,Y,Z) Return a string formed by substituting string Z for every occurrance of string Y in string X. The BINARY collating sequence is used for comparison" --- test

[sqlite] Limit selection by rolling sum?

Hey all -- I have a table that I would like to select the first N records where the rolling sum of a given column is less than some literal value. SQL for this might look like: select item_id from items where rolling_sum(item_size) < 1 order by item_name; Is there a way to do this? Would s

RE: [sqlite] Re: Table with 2 primary keys... what's the problem?

> -Original Message- > From: Igor Tandetnik [mailto:[EMAIL PROTECTED] > Sent: Saturday, May 12, 2007 9:41 PM > To: SQLite > Subject: [sqlite] Re: Table with 2 primary keys... what's the problem? > > Darren Duncan <[EMAIL PROTECTED]> wrote: > > At 11:37 PM +0100 5/12/07, Paulo J. Matos wrot

Re: [sqlite] Different VDBE opcodes for the same query (part 2)

--- "Sergey M. Brytsko" <[EMAIL PROTECTED]> wrote: > Hi All! > > The DB schema is: > CREATE TABLE xxx(a TEXT, b INTEGER, c TEXT); > CREATE INDEX idx on xxx(b); > > explain query plan select rowid, a, b, c from xxx where b > 1 order by > rowid; > 0|0|TABLE xxx USING PRIMARY KEY ORDER BY > T

[sqlite] Many small queries vs fewer large queries

Traditionally we've found that it's better to issue a few larger queries against a database (such as MSSQL or Oracle) even when the results required some processing to separate out the data because much of the cost of running a query was communication and networking overhead. Since SQLite is an i

Re: [sqlite] WG: indexing large databases

--- Juri Wichanow <[EMAIL PROTECTED]> wrote: > > In my database of 30 000 000 records. > > At " Pragma cache_size = 100 " indexation lasts > 12 hours, > > at " Pragma cache_size = 2000 " - 45 minutes. It would be interesting if you ran a profiler such as gprof during each run to see where

[sqlite] One more SQLite threading question

Hello, I have tried to search all the documentation about threading in SQLite, but I'm still somewhat confused. It's often suggested to create a pool of sqlite3 structures, but what if I would like to have only only sqlite3 connection and serialize all the DB operations to one thread (name it 'A

[sqlite] Different VDBE opcodes for the same query (part 2)

Hi All! The DB schema is: CREATE TABLE xxx(a TEXT, b INTEGER, c TEXT); CREATE INDEX idx on xxx(b); explain query plan select rowid, a, b, c from xxx where b > 1 order by rowid; 0|0|TABLE xxx USING PRIMARY KEY ORDER BY The index is not used?! explain query plan select rowid, a, b, c from xxx