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
> ot
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 n
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.
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 o
Hi SQLite users,
Questions:
1. What is the preferred way to copy/flush new memory db to disk db ? (all
tables, indices, records from memoryDB to diskDB)
2. Should I create indices first in memory db or directly in disk db ?
3. How to maintain exclusive access to disk db file till creation/copying
5 matches
Mail list logo