- Original Message
From: Unit 5 <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Thursday, November 9, 2006 8:02:51 AM
Subject: RE: [sqlite] Insert statement taking too long
> --- Robert Simpson <[EMAIL PROTECTED]> wrote:
> > You need to create an index
Unit 5 uttered:
--- Robert Simpson <[EMAIL PROTECTED]> wrote:
You need to create an index on the columns you're
joining. Otherwise I
believe 100,000,000 rows (10k x 10k) in table 2 will
be scanned while SQLite
looks for matches against the 10,000 rows in table
1.
While that makes sense, I
--- Robert Simpson <[EMAIL PROTECTED]> wrote:
> You need to create an index on the columns you're
> joining. Otherwise I
> believe 100,000,000 rows (10k x 10k) in table 2 will
> be scanned while SQLite
> looks for matches against the 10,000 rows in table
> 1.
While that makes sense, I suspect
Wednesday, November 08, 2006 10:47 PM
> To: sqlite-users@sqlite.org
> Subject: [sqlite] Insert statement taking too long
>
> Hello,
>
> I am seeing an interesting performance issue with
> INSERT statements. I am using Sqlite 3.3.5 on a
> Windows XP box. Here is a brief summar
Hello,
I am seeing an interesting performance issue with
INSERT statements. I am using Sqlite 3.3.5 on a
Windows XP box. Here is a brief summary of the
situation:
Insert statements that require no join are quite fast:
a) I create an empty table (drop it first if it
exists).
b) INSERT ... SELECT
5 matches
Mail list logo