> If the performance problem is with the seconday index, is there a way to
> "pause" indexing before
> a large bulk insert and then "resume" it later without rebuilding the entire
> index (to avoid
> doing: drop index + inserts + create index)?
No
[EMAIL PROTECTED] wrote:
> > - Original Message
> > From: Joe Wilson <[EMAIL PROTECTED]>
> > To: sqlite-users@sqlite.org
> > Sent: Monday, June 11, 2007 8:36:32 PM
> > Subject: Re: [sqlite] Database replication question
> >
> >
> >
[EMAIL PROTECTED] wrote:
- Original Message
From: Joe Wilson <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Monday, June 11, 2007 8:36:32 PM
Subject: Re: [sqlite] Database replication question
Large bulk inserts with more than one index (implicit or explicit)
is not SQ
[EMAIL PROTECTED] wrote:
>
> The table I have is something like
> CREATE TABLE sn2uid(
>sn VARCHAR(100) NOT NULL,
>uid INTEGER NOT NULL,
>PRIMARY KEY (sn)
> );
> CREATE INDEX uidindex on sn2uid ( uid )
>
>
> is there a way to do a select or a .dump so that when inserting the
> data
> - Original Message
> From: Joe Wilson <[EMAIL PROTECTED]>
> To: sqlite-users@sqlite.org
> Sent: Monday, June 11, 2007 8:36:32 PM
> Subject: Re: [sqlite] Database replication question
>
>
> Large bulk inserts with more than one index (implicit or expli
Large bulk inserts with more than one index (implicit or explicit)
is not SQLite's strong suit.
If you search the mailing list archives you'll find a few suggestions:
- "BEGIN EXCLUSIVE" (or is it "BEGIN IMMEDIATE"?) on the
database file and then copy the file over - fastest way
or
-
Hi all
I am trying to put in place a simple replication process to copy a database
from one machine to an other.
The table I have is something like
CREATE TABLE sn2uid(sn VARCHAR(100) NOT NULL, uid INTEGER NOT NULL, PRIMARY KEY
(sn));
CREATE INDEX uidindex on sn2uid ( uid )
Where the (sn,uid)
7 matches
Mail list logo
