Re: [sqlite] [OT] Shell globbing - Re: [sqlite] trying to compile SQLite

2004-09-05 Thread Greg Miller
Christian Smith wrote: On Fri, 3 Sep 2004, Greg Miller wrote: I guess the UNIX folks just didn't know any better way back then. Putting globbing in the API instead of the shell is a much better approach, but that wasn't all that obvious when UNIX first came along. You condone the DOS/Windows

[sqlite] temporary databases

2004-09-05 Thread Miguel Angel Latorre Díaz
Shouldn't vdbeaux.c line 753: rc = sqlite3BtreeFactory(db, ":memory:", 0, TEMP_PAGES, >pBtree); obey the TEMP_STORE macro so it is stored either in memory or disk? I know it's there for speed, but that's what TEMP_STORE is for. Isn't it? If I change in that line the ":memory:" to a 0 (zero),

Re: [sqlite] LIMIT does not speed up query execution

2004-09-05 Thread D. Richard Hipp
hilaner wrote: And - if I have to have sorted results as a small (but ordered!) part of big amount of data - there is no way to make it faster... SQLite will pull records out of the database in sorted order, if you have an index on the columns of the ORDER BY clause and you don't need to use a

Re: [sqlite] LIMIT does not speed up query execution

2004-09-05 Thread hilaner
Christian Smith wrote: > Query (2) has an extra condition in the WHERE clause, thus reducing > the result set size to be sorted. As sorting is probably an > O(n.log(n)) operation, halving the result set will more than halve > the time taken to sort, for example. Add that extra condition to >

Re: [sqlite] Re: [sqlite3] Conditional jump or move depends on uninitialised value(s)

2004-09-05 Thread Tiago Dionizio
Thanks for the clarification. I finally found the problem... i was assuming the sqlite3_context pointer for the step/finalize callbacks of aggregate functions was always the same and was saving it (on the step callback) for future use. Updating that pointer fixed things - all works just fine and

Re: [sqlite] LIMIT does not speed up query execution

2004-09-05 Thread Christian Smith
On Sat, 4 Sep 2004, Darren Duncan wrote: >So to make this faster you either have to make WHERE return fewer >rows (better), or let it return more but remove the ORDER BY. It's not a good idea to use LIMIT on unordered results, of course, as the order of results for unordered result sets is,

[sqlite] Re: [sqlite3] Conditional jump or move depends on uninitialised value(s)

2004-09-05 Thread D. Richard Hipp
Tiago Dionizio wrote: Using: SQLite 3 from cvs Fedora Core 2 gcc 3.3.3 I am currently working on trying to bind sqlite3 to Lua, and while testing things i encountered some problems regarding uninitialised values in the sqlite library. These tests were done using user defined functions, and more