Re: [sqlite] grouping inserts vs. one large tranaction

2010-09-18 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/18/2010 01:45 PM, Erik Fears wrote: > but I've found that during a write transaction readers are locked from > reading the database. I suggest reading the following two pages: http://www.sqlite.org/lockingv3.html http://www.sqlite.org/wal.h

Re: [sqlite] VACUUM can actually increase the DB file?

2010-09-18 Thread Jay A. Kreibich
On Sat, Sep 18, 2010 at 11:36:12AM -0700, Kyle McKay scratched on the wall: > On Sep 17, 2010, at 16:08:42 PDT, Oliver Schneider wrote: > > just a few minutes ago I ran a VACUUM on a DB file and the size before > > was 2089610240 and afterwards 2135066624. Is this normal? > Admittedly that's only

Re: [sqlite] Mozilla History Autodelete -

2010-09-18 Thread Simon Slavin
On 18 Sep 2010, at 10:58pm, Blizza wrote: > Hey mates HI THERE . > > I really need help , please . > > Why my history deletes itself ? And how to regain it ? Your question is about FireFox. There's nothing in SQLite that restricts things to . You will get better help asking in a forum

Re: [sqlite] Mozilla History Autodelete -

2010-09-18 Thread Blizza
Hey mates HI THERE . I really need help , please . Why my history deletes itself ? And how to regain it ? -- From: "All Marri" Sent: Wednesday, September 08, 2010 12:45 PM To: Subject: Re: [sqlite] Mozilla History Autodelete > > Hi , I am SORRY

[sqlite] grouping inserts vs. one large tranaction

2010-09-18 Thread Erik Fears
sqlite-users, I've got a multi-threaded daemon that's inserting large batches into a table that looks like this: CREATE TABLE list_node (key INTEGER PRIMARY KEY, name TEXT UNIQUE, list INT); There's one writer thread, and one reader thread. Each thread would have its own db object. The very fir

Re: [sqlite] VACUUM can actually increase the DB file?

2010-09-18 Thread Richard Hipp
On Sat, Sep 18, 2010 at 2:36 PM, Kyle McKay wrote: > On Sep 17, 2010, at 16:08:42 PDT, Oliver Schneider wrote: > > just a few minutes ago I ran a VACUUM on a DB file and the size before > > was 2089610240 and afterwards 2135066624. Is this normal? > > I've recently been noticing the same thing, f

Re: [sqlite] VACUUM can actually increase the DB file?

2010-09-18 Thread Kyle McKay
On Sep 17, 2010, at 16:08:42 PDT, Oliver Schneider wrote: > just a few minutes ago I ran a VACUUM on a DB file and the size before > was 2089610240 and afterwards 2135066624. Is this normal? I've recently been noticing the same thing, for example: 443182080 newdb.sq3 $ sqlite3 newdb.sq3 SQLite ve

Re: [sqlite] PATCH: sqlite3_table_column_metadata does not return the default column value.

2010-09-18 Thread Jay A. Kreibich
On Fri, Sep 17, 2010 at 06:32:13PM +, Cesar Crusius scratched on the wall: > In one of my applications I have the need to know what is the > declared default value for any given column. The default expression is also available from PRAGMA table_info(). -j -- Jay A. Kreibich < J A Y @

[sqlite] PATCH: sqlite3_table_column_metadata does not return the default column value.

2010-09-18 Thread Cesar Crusius
In one of my applications I have the need to know what is the declared default value for any given column. I have patched my SQLite copy but I think this would be something worth putting in the official code. I'm attaching the changes, which are very simple. Best, - Cesar --- a/sqlite3.c +++

Re: [sqlite] VACUUM can actually increase the DB file?

2010-09-18 Thread Max Vlasov
> just a few minutes ago I ran a VACUUM on a DB file and the size before > was 2089610240 and afterwards 2135066624. Is this normal? > > If you have a copy of the old db and new db, can you check the results on both databases of the following pragmas: PRAGMA freelist_count; PRAGMA integrity_check;