Re: [sqlite] Order Statistic Trees

Sorry for the incomplete post, stupid phone. On May 17, 2014 8:40 PM, "Simon Slavin" wrote: > Just want to check: this is what it sounds like, right ? Your user has a window open where they are scrolling through the table, ordered by SomeColumn. You need to know whether

Re: [sqlite] Order Statistic Trees

Sorry, I typoed the second query. Should have been <=. On May 17, 2014 8:40 PM, "Simon Slavin" wrote: > > On 18 May 2014, at 3:19am, Scott Robison wrote: > > > It is easy enough to read the source data and insert it into a table. It > is > > easy

Re: [sqlite] Order Statistic Trees

On 18 May 2014, at 3:19am, Scott Robison wrote: > It is easy enough to read the source data and insert it into a table. It is > easy enough to query the list of data ordered by any field after the data > has been completely read. The hard part is knowing the correct

[sqlite] Order Statistic Trees

My apologies for this lengthy email. I hope someone can wade through it and provide some insight. For many database manipulation needs, SQLite (or SQL in general) is a perfectly adequate solution. I'm having a problem that does not work well in SQL land (or at least I can't find a solution that

Re: [sqlite] Pre-preparing querys

On Sat, May 17, 2014 at 4:55 PM, Baruch Burstein wrote: > What is the overhead of holding open a prepared statement? If my program is > not time critical at all (it is mostly UI bound), but every once in a while > (anywhere from 10 times a second to once every 10 minutes) it

[sqlite] Suggestion for shell .IMPORT improvement

Hello, When .importing from a csv file (for example) with a command like ".import data.csv data" if the table does not exist, the table is created using the first row of data.csv as the field names. But if the same file is imported a second time, the first line is treated as data. My

Re: [sqlite] Pre-preparing querys

On 17 May 2014, at 9:55pm, Baruch Burstein wrote: > What is the overhead of holding open a prepared statement? If my program is > not time critical at all (it is mostly UI bound), but every once in a while > (anywhere from 10 times a second to once every 10 minutes) it

[sqlite] Pre-preparing querys

What is the overhead of holding open a prepared statement? If my program is not time critical at all (it is mostly UI bound), but every once in a while (anywhere from 10 times a second to once every 10 minutes) it needs to run a few querys, would it make more sense to prepare all of the querys

[sqlite] Shared-Cache Mode

Hello, Is there any way to known if one connection participate to shared-cache mode ? I've read http://sqlite.org/sharedcache.html which specifies how to set but not how to get the mode! Regards. ___ sqlite-users mailing list sqlite-users@sqlite.org