Am Donnerstag, den 22.09.2011, 20:28 +0100 schrieb Simon Slavin:
> Indexes are not recreated from scratch unless you explicitly ask for them to
> be (rare). If you open a database with a million rows in and add or change a
> row, the indexes for that table are each modified slightly to reflect
On 22 Sep 2011, at 8:11pm, JM wrote:
> is the index updated after each insert/update/delete operation or is
> it updated after the transaction containing (many of) these operations
> has been committed? That way an insertion of many lines into the
> database would take time for index recreation
Thanks for your replies! They were very helpful!
But is the index updated after each insert/update/delete operation or is
it updated after the transaction containing (many of) these operations
has been committed? That way an insertion of many lines into the
database would take time for index
On 22 Sep 2011, at 5:30pm, Jay A. Kreibich wrote:
> Indexes are updated automatically.
As they are with all implementations of SQL. That's why you didn't see it
documented: nobody thought there was any question.
> Note: this means indexes will
> speed up queries, but incur a performance
On Thu, Sep 22, 2011 at 06:17:06PM +0200, JM scratched on the wall:
> Hello All
>
> I'm relatively new to sqlite and database stuff and I have a question
> concerning indices in sqlite:
>
> If I create an index for a table to speed up searches, etc. and then do
> writing operation on that table
Hello All
I'm relatively new to sqlite and database stuff and I have a question
concerning indices in sqlite:
If I create an index for a table to speed up searches, etc. and then do
writing operation on that table (including removals and changes of
lines), will I have to remove and recreate the
6 matches
Mail list logo
