RE: [sqlite] Preferred way to copy/flush new memory db to disk db ?

2006-06-29 Thread Denis Povshedny
Maybe you shall open in sqlite3_open a temporary file as a database
file? And move it to destination in case of success

WBR,
Denis
---


My requirements are 
 database file must be removed from disk if any error while 
 creating/copying tables, records or indices
 other application or other instance of same app must not be able to
access
 the database, till 
 database is not ready with necessary minimum tables and records. 

So to avoid other app accessing, I thought of creating memory db. Rohit
-- 



Re: [sqlite] Preferred way to copy/flush new memory db to disk db ?

2006-06-28 Thread RohitPatel9999

My requirements are 
 database file must be removed from disk if any error while
 creating/copying tables, records or 
 indices 
 other application or other instance of same app must not be able to access
 the database, till 
 database is not ready with necessary minimum tables and records. 

So to avoid other app accessing, I thought of creating memory db.
Rohit
-- 
View this message in context: 
http://www.nabble.com/Preferred-way-to-copy-flush-new-memory-db-to-disk-db---tf1843573.html#a5081614
Sent from the SQLite forum at Nabble.com.



Re: [sqlite] Preferred way to copy/flush new memory db to disk db ?

2006-06-28 Thread Jay Sprenkle

On 6/28/06, RohitPatel [EMAIL PROTECTED] wrote:


My requirements are
 database file must be removed from disk if any error while
 creating/copying tables, records or
 indices
 other application or other instance of same app must not be able to access
 the database, till
 database is not ready with necessary minimum tables and records.

So to avoid other app accessing, I thought of creating memory db.


Just write it to use the disk. It's not dramatically slower and you don't need
to write code to flush and load the database.


Re: [sqlite] Preferred way to copy/flush new memory db to disk db ?

2006-06-25 Thread C.Peachment
On Sun, 25 Jun 2006 01:58:10 -0700 (PDT), RohitPatel wrote:

Intial database will have about 30+ tables, very few records in each of
these tables, one or two indices on some tables.

For such a small database, why not create it directly on disk? The
time required should be just a one second or two.

Remember to start the command sequence with begn transaction
and finish with commit transaction.

Chris