Re: [sqlite] unexpected large journal file

On Fri, Jun 18, 2010 at 5:24 PM, Eric Smith wrote: > Jay A.  Kreibich wrote: >> Yes.  Hence the "and this is the important part" comment.  Most of >> the time when people are building billion-row files, they're building >> a new DB by importing a static source of data.  If

Re: [sqlite] unexpected large journal file

On Fri, Jun 18, 2010 at 08:24:47PM -0400, Eric Smith scratched on the wall: > Jay A. Kreibich wrote: > > > Yes. Hence the "and this is the important part" comment. Most of > > the time when people are building billion-row files, they're building > > a new DB by importing a static source of

Re: [sqlite] unexpected large journal file

Jay A. Kreibich wrote: > Yes. Hence the "and this is the important part" comment. Most of > the time when people are building billion-row files, they're building > a new DB by importing a static source of data. If things go wrong, > you just throw out the database and try again. That's

[sqlite] BUG REPORT: alter2 test does not run with SQLITE_HAS_CODEC

Line 25 of alter2.test has the following comment: # These tests do not work if there is a codec. # #if {[catch {sqlite3 -has_codec} r] || $r} return Either the comment on line 25 is incorrect, or should line 27 should be uncommented Please advise, Noah CONFIDENTIALITY NOTICE: This

Re: [sqlite] unexpected large journal file

Simon Slavin wrote: > How do you pass the handle from your C code to your Tcl code ? I don't. I pass it from Tcl to C. The handle in Tcl is a command name registered with the interpreter. SQLite attaches a structure to the registration that contains the underlying handle as used by the

Re: [sqlite] unexpected large journal file

On 18 Jun 2010, at 8:47pm, Eric Smith wrote: > Don't know what I was thinking when I typed that. I'm sharing a > connection in a single thread, mixing C API calls and Tcl API calls. > The C API calls drive the INSERTs; Tcl API calls drive BEGIN/COMMIT How do you pass the handle from your C

Re: [sqlite] unexpected large journal file

On Fri, Jun 18, 2010 at 04:07:53PM -0400, Eric Smith scratched on the wall: > Jay A. Kreibich wrote: > > > > I'd really love to avoid writing a big journal file. And I'd love to > > > avoid doing a billion-row insert in one transaction. > > > > So turn journaling off. > > ... which implies

Re: [sqlite] unexpected large journal file

Jay A. Kreibich wrote: > > I'd really love to avoid writing a big journal file. And I'd love to > > avoid doing a billion-row insert in one transaction. > > So turn journaling off. ... which implies possible corruption on app failure, right? I want progress to be saved every once in a

Re: [sqlite] unexpected large journal file

On Fri, Jun 18, 2010 at 03:37:19PM -0400, Eric Smith scratched on the wall: > I have no user-defined indices in my db, and want to do a largish number > of inserts (a few billion). I COMMIT every 10 million INSERTs or so -- > so if my app dies (or I want to kill it) I don't have to start over.

Re: [sqlite] unexpected large journal file

Terribly sorry to self-reply, but I have a correction: > I'm using the Tcl API, which probably doesn't matter for this question. Don't know what I was thinking when I typed that. I'm sharing a connection in a single thread, mixing C API calls and Tcl API calls. The C API calls drive the

[sqlite] unexpected large journal file

I have no user-defined indices in my db, and want to do a largish number of inserts (a few billion). I COMMIT every 10 million INSERTs or so -- so if my app dies (or I want to kill it) I don't have to start over. Row sizes are small, a couple hundred bytes across 15ish columns. The primary