[sqlite] Where is the database file created?

Hi, I read the documentation, features and faq and could not find anything that specifies where (which directory) the database file is stored. I launched sqlite3.exe on windows without a database name, using the '.databases' command, I get: sqlite .databases seq name file ---

Re: [sqlite] Where is the database file created?

On Sat, Mar 22, 2008 at 06:44:45PM +0900, Fred Janon wrote: Hi, I read the documentation, features and faq and could not find anything that specifies where (which directory) the database file is stored. I launched sqlite3.exe on windows without a database name, using the '.databases'

Re: [sqlite] Where is the database file created?

Thanks, I did already read that page and all the other ones. I was asking a question about SQLLite3.exe very precisely, I thought. The command line is in my email and its result. I don't think there is any mention of in-memory database in the feature list either. I thought it might help to improve

[sqlite] How to determine current lock state

Hello, Is there a way to determine current lock state of a database? More specifically, I’d like to be able to tell whether the main database in the current session is under SHARED lock, or under RESERVED/PENDING/EXCLUSIVE lock. This is needed for unit tests and assertions. Thanks!

Re: [sqlite] Where is the database file created?

On Sat, 22 Mar 2008 22:06:12 +0900, Fred Janon [EMAIL PROTECTED] wrote: Thanks, I did already read that page and all the other ones. I was asking a question about SQLLite3.exe very precisely, I thought. The command line is in my email and its result. I don't think there is any mention of in-memory

[sqlite] Shared cache benefit question

I have a heavily threaded app (I know, evil) where there might be 50 threads accessing 10 databases. Each thread always calls sqlite3_open when it starts working with a database and sqlite3_close when it's done (so no sharing of handles across threads). A thread might have two or more handles

Re: [sqlite] Where is the database file created?

Fred Janon [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] and since it doesn't show a file, I presume that sqlite does actually support in-memory temporary databases? Yes. Where is is documented? http://sqlite.org/c3ref/open.html the paragraph that mentions :memory: database.

Re: [sqlite] delete on view

Ok, I've removed that nested DELETE command. Now I have still the problem that I can't delete tablenames with multiple field entries. The full sql I have is as follows: --- create table dbapp_tablenames ( tablenameID integer primary key, tablename text not null unique on conflict ignore );

Re: [sqlite] Where is the database file created?

On Sat, 22 Mar 2008 22:06:12 +0900, you wrote: The command line is in my email and its result. I don't think there is any mention of in-memory database in the feature list either. I thought it might help to improve the documentation. I agree the http://sqlite.org/quickstart.html page should

Re: [sqlite] delete on view

Fabiano Sidler [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] sqlite select * from dbapp; employees|name,surname sqlite delete from dbapp where tablename='employees' and fields='surname'; sqlite delete from dbapp where tablename='employees' and fields='surname'; sqlite delete

Re: [sqlite] delete on view

Igor Tandetnik schrieb: You don't have a single row in dbapp view that has fields='surname'. The only record you have is one where fields='name,surname'. So no row matches condition, and thus no row gets deleted. Your trigger never even runs. That's weird. So Sqlite first does read from

Re: [sqlite] delete on view

Fabiano Sidler [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Igor Tandetnik schrieb: You don't have a single row in dbapp view that has fields='surname'. The only record you have is one where fields='name,surname'. So no row matches condition, and thus no row gets deleted. Your

Re: [sqlite] Multiple Row Updates

On Fri, Mar 21, 2008 at 07:09:29PM -0600, John Stanton scratched on the wall: Use this sequence - sqlite3_prepare_v2 while not finished sqlite3_bind_xxx sqlite3_step until SQLITE_DONE sqlite3_reset repeat sqlite3_finalize The sqlite3_reset

Re: [sqlite] Shared cache benefit question

Just give it a try and see what happens. You just need to enable the shared cache once. I'd think the blocking would not be any different with the shared cache enabled. But you should get reduced I/O load since the cache will be larger and accessible to all threads. HTH, Ken