Re: [sqlite] Is it safe to read or write a table while being indexed?

Hi Christian, On 18/04/2006, at 8:22, Christian Smith wrote: SQLite will make possible whatever is safe. Just be prepared to handle SQLITE_BUSY and SQLite will take care of the rest. Great. This is what I do now. No worries here then... If the indexing process uses a large SQLite cache

Re: [sqlite] Is it safe to read or write a table while being indexed?

On Sat, 15 Apr 2006, Tito Ciuro wrote: >Hello, > >I was wondering whether it is safe to read or write a table while >being indexed. Here's a scenario: for batch imports, it's sometimes >better to DROP the indexes, do the INSERTs and then recreate the >relevant indexes. Indexing may take a little

Re: [sqlite] Is it safe to read or write a table while being indexed?

On 16/04/2006, at 3:52, [EMAIL PROTECTED] wrote: Tito Ciuro <[EMAIL PROTECTED]> wrote: - Does SQLite acquire an EXCLUSIVE lock when indexing? Yes - If I'm not mistaken, an EXCLUSIVE lock does not stop other readers from accessing the database. You are mistaken. An EXCLUSIVE lock means

Re: [sqlite] Is it safe to read or write a table while being indexed?

Tito Ciuro <[EMAIL PROTECTED]> wrote: > Hello, > > I was wondering whether it is safe to read or write a table while > being indexed. Here's a scenario: for batch imports, it's sometimes > better to DROP the indexes, do the INSERTs and then recreate the > relevant indexes. Indexing may take

[sqlite] Is it safe to read or write a table while being indexed?

Hello, I was wondering whether it is safe to read or write a table while being indexed. Here's a scenario: for batch imports, it's sometimes better to DROP the indexes, do the INSERTs and then recreate the relevant indexes. Indexing may take a little bit of time, so I was wondering if: