Re: [sqlite] new sqlite-based webserver

Hi, yes i know, the problem is, its single-threaded (because of protability), so if anyone starts a download with a slow connection, the server is blocked for other connections.. im still thinking about this problem... single-threading whle rendering th pages and multithreading for sending

Re: [sqlite] Re: SQLite Order BY

A. Pagaltzis wrote: * John Stanton [EMAIL PROTECTED] [2006-10-09 19:35]: Sorting data is time consuming, a physical law is involved. At best it is an nlog(n) process. Only when you sort by comparing elements with each other. Bucket sort runs in O(n), f.ex. And quantum sort is O(1).

[sqlite] Re: any questions

mimuel1 said the following, On 2006-10-09 13:07: - who knows links with the thema: from access to SQLite? Kexi (kexi-project.org) is designed with this task in mind. Other projects: http://www.sqlite.org/cvstrac/wiki?p=SqliteUsers -- regards / pozdrawiam, Jaroslaw Staniek Sponsored by

Re: [sqlite] new sqlite-based webserver

John Stanton wrote: Martin Jenkins wrote: Seems ok now. Quite fast even. It is still dead. Address 62.194.135.186 doesn't respond. Traceroute fails. Odd. It's still working here (UK). DNSStuff reports a different address though (62.104.138.84) and a traceroute from there is fine (13 hops).

[sqlite] wxSqlite- Long Insertion time

Hi All, I am using wxSqlite to develop my application. I have an insert query in my application. It adds a 16 seconds overhead to my application, otherwise it executes in 20 seconds. (Now it needs 36 seconds!). Where could be the problem? The insert query is executing only 1000 times. Thanks,

Re: [sqlite] wxSqlite- Long Insertion time

Lloyd wrote: Where could be the problem? The insert query is executing only 1000 times. Are these inserts in 1 transaction or 1000? If the latter then it will take a long time because sqlite has to wait 1000 times for the data to be written to the disk. It's generally accepted that this

[sqlite] SQLite on RAM

Hi List, Is it possible to use SQLite on RAM (where there is no file system) i.e. directly on memory, (No Hard disk). I am planning to use it on RAM inside TV. How it will read and write on RAM. Thanks and Regards, Vivek R

Re: [sqlite] new sqlite-based webserver

Gunter, I recently wrote a multi-threaded portable web server in simpl ANSI C. It uses Win32 threads or pthreads. It caches threads and re-uses them on a most recently used basis. Efficiency is obtained by using TransmitFile (Win32) or sendfile (Unix). The logic is simple for an

RE: [sqlite] SQLite on RAM

Believe so, in this case you would use an 'in memory' database. This can be opened by giving the filename :memory:. There is more information on the wesite and in the mail archive on this. Personally I have never used this feature, so cant really offer more help than that. -Original

Re: [sqlite] new sqlite-based webserver

Martin Jenkins wrote: John Stanton wrote: Martin Jenkins wrote: Seems ok now. Quite fast even. It is still dead. Address 62.194.135.186 doesn't respond. Traceroute fails. Odd. It's still working here (UK). DNSStuff reports a different address though (62.104.138.84) and a traceroute

[sqlite] Terminating long query in C ?

Hi, How do I cancel a long running query? In OLEDB I can call pICommand-Cancel() from a different thread to kill the running query. How can I do the same in SQLite? thanks. Radzi.

Re: [sqlite] new sqlite-based webserver

John Stanton wrote: Martin Jenkins wrote: John Stanton wrote: Martin Jenkins wrote: Seems ok now. Quite fast even. It is still dead. Address 62.194.135.186 doesn't respond. Traceroute fails. Odd. It's still working here (UK). DNSStuff reports a different address though

Re: [sqlite] new sqlite-based webserver

Dennis Cote wrote: It's a little slow, taking about 10 seconds to load, but not too bad. About 4-5 seconds here but the wires are shorter ;) Martin - To unsubscribe, send email to [EMAIL PROTECTED]

Re: [sqlite] Terminating long query in C ?

Mohd Radzi Ibrahim wrote: How do I cancel a long running query? In OLEDB I can call pICommand-Cancel() from a different thread to kill the running query. How can I do the same in SQLite? Radzi, See http://www.sqlite.org/capi3ref.html#sqlite3_interrupt for information on

[sqlite] Re: Terminating long query in C ?

Mohd Radzi Ibrahim [EMAIL PROTECTED] wrote: How do I cancel a long running query? There are two ways I know of. You can register a progress handler - see sqlite3_progress_handler. The handler is called periodically while the query is running, and has the option to interrupt the query.

Re: [sqlite] Terminating long query in C ?

Igor Tandetnik [EMAIL PROTECTED] wrote: Another way is to use sqlite3_interrupt. Before SQLite 3.3.7 (which I believe is the latest version at this time) 3.3.8 was released yesterday (Monday) morning. I have not sent out an official announcement on this mailing list. Sorry.

[sqlite] Re: Terminating long query in C ?

[EMAIL PROTECTED] wrote: sqlite3_interrupt() has long been used by the sqlite3 shell program. When you press control-C a posix signal handler invokes sqlite3_interrupt() to stop the current query. (This only works on posix, of course.) The original purpose of sqlite3_interrupt() was to support

Re: [sqlite] Re: Terminating long query in C ?

Thank you guys for the suggestion. That's what I really need. Which one is better, the sqlite3_interrupt() or sqlite3_progress_handler()? My gut feeling is that sqlite3_interrupt() should be better since it does not interfere with the running of the query until it is signaled. Besides, the

[sqlite] What causes xConnect and xDisconnect to actually get invoked? (Virtual Tables)

I realize that the virtual table implementation is currently experimental, but I've been added them into a project of mine (which will end up public when it's done), and I don't truly understand the purpose of the xConnect and xDisconnect callbacks, when compared with their xCreate and xDestroy

Re: [sqlite] What causes xConnect and xDisconnect to actually get invoked? (Virtual Tables)

Michael Brehm [EMAIL PROTECTED] wrote: I realize that the virtual table implementation is currently experimental, but I've been added them into a project of mine (which will end up public when it's done), and I don't truly understand the purpose of the xConnect and xDisconnect callbacks, when

Re: [sqlite] wxSqlite- Long Insertion time

Are these inserts in 1 transaction or 1000? Yes it is in 1000 transactions. For me consistancy, atomicity...(ACID) are not a problem. But the speed of operation is major constraint. How can I achieve speed in insertion cases like this? Thanks for your informative reply. Lloyd. On Tue,

Re: [sqlite] Re: Terminating long query in C ?

Tuesday, October 10, 2006, 9:32:18 PM, Mohd Radzi Ibrahim wrote: Thank you guys for the suggestion. That's what I really need. Which one is better, the sqlite3_interrupt() or sqlite3_progress_handler()? My gut feeling is that sqlite3_interrupt() should be better since it does not interfere

RE: [sqlite] What causes xConnect and xDisconnect to actually get invoked? (Virtual Tables)

Ahhh... I see now. I didn't realize that the virtual table persisted in the database until explicitly dropped, I thought they were volatile entities like temp tables. The entire module concept makes a great deal more sense to me now as well. I believe I can finally see how it all works together.