Re: [sqlite] Re: Life of a cursor

Hello George, After that, it's of no use to keep the database open, so it closes it. And sends the results obtained back to the client. Wow! This is the first I hear that. Wouldn't that be an expensive operation? (opening, closing, reopening...) Thanks for your comments! Regards, -- Tito On 19 m

[sqlite] Re: Life of a cursor

Hello Tito, >> Would you expect a cursor to live after is database has been closed? Sure. Imagine a Client - Server scenario: the client makes a request (e.g. SELECT * FROM Orders), request which is passed to a server. The server executes the sql and obtains a recordset. After that, it's of no

RE: [sqlite] Newbie questions

>>The sqlite_compile/step/finalize paradigm allows (requires really ) >>forward browsing through a result set. The results from sqlite_get_table() allow random access, should this be required, and I have even had success using qsort() on the results to re-order them without needing to re-query th