Re: [sqlite] BUG with unnecessary brackets in queries with IN ( SELECT .. )

2014-06-11 Thread beell
Gesendet: Mittwoch, 11. Juni 2014 um 10:29 Uhr Von: RSmith An: sqlite-users@sqlite.org Betreff: Re: [sqlite] BUG with unnecessary brackets in queries with IN ( SELECT .. ) >On 2014/06/11 07:48, be...@web.de wrote: Simple example : Working (correct result)

Re: [sqlite] What is the recommended size we should keep aside for sqlite journal

2014-06-11 Thread Richard Hipp
On Wed, Jun 11, 2014 at 4:08 AM, Mayank Kumar (mayankum) wrote: > Thanks Richard. When there is not enough space to write a journal file, > what is the expected behavior. Will that and any transaction which cannot > write a journal file fail ? > > You will get an

Re: [sqlite] BUG with unnecessary brackets in queries with IN ( SELECT .. )

2014-06-11 Thread RSmith
On 2014/06/11 07:48, be...@web.de wrote: Simple example : Working (correct result) select id from tbl where id in (select id from tbl) NOT working (incorrect result) : select id from tbl where id in ( ( select id from tbl) ) In the first query, SQLite looks for values of "id" that are in

Re: [sqlite] What is the recommended size we should keep aside for sqlite journal

2014-06-11 Thread Mayank Kumar (mayankum)
Thanks Richard. When there is not enough space to write a journal file, what is the expected behavior. Will that and any transaction which cannot write a journal file fail ? -Mayank -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On

Re: [sqlite] Building multiple indexes in one scan over a table

2014-06-11 Thread Paul
> > > CREATE INDEX samples_by_time ON samples(time); > CREATE INDEX samples_by_name ON samples(name_id); > CREATE INDEX samples_by_type ON samples(type_id); > > Maybe this is dumb idea (sorry for

Re: [sqlite] Building multiple indexes in one scan over a table

2014-06-11 Thread Markus Schaber
Hi, > Von: Fabian Giesen > I'm working on a profiler that uses SQLite to store and index the > results. > > Due to the nature of the task, the workload ends up splitting into > essentially three phases: > > 1. Bulk insertion of relatively large amounts of data (low hundreds > of megabytes to