On Wed, 2005-05-04 at 17:21 -0400, Patrick Dunnigan wrote:
> Is this also true for for in memory databases?
No. ":memory:" databases are fast regardless of whether
or not your INSERT statements are enclosed in BEGIN..COMMIT.
Since ":memory:" databases do not have to worry about being
atomic and
Is this also true for for in memory databases?
- Original Message -
From: "D. Richard Hipp" <[EMAIL PROTECTED]>
To: <sqlite-users@sqlite.org>
Sent: Wednesday, May 04, 2005 5:03 PM
Subject: Re: [sqlite] how to COPY FROM stdin in 3.x?
On Wed, 2005-05-04 at 13:4
On Wed, 2005-05-04 at 13:49 -0700, Darren Duncan wrote:
> At 1:27 PM -0700 5/4/05, scott wrote:
> >I can rewrite this to do individual inserts, but would like to find
> >out whether there's a better workaround/idiom for this.
>
> If you are going to use an INSERT statement, then your usage is a
At 1:27 PM -0700 5/4/05, scott wrote:
I can rewrite this to do individual inserts, but would like to find
out whether there's a better workaround/idiom for this.
If you are going to use an INSERT statement, then your usage is a
prime candidate to use prepared statements with. Your insert
According to http://www.sqlite.org/lang_copy.html, COPY FROM has been
removed in 3.0 because of UTF8/16 difficulties. The command-line
workaround won't help in my situation because I need to bulk insert
from a C++ program.
I couldn't find any reference to COPY FROM SQL workarounds in the
5 matches
Mail list logo
