Re: [sqlite] SQLite3 Bug Report: The shell accepts some dot commands ending in semicolons while rejecting others.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28/01/13 21:11, Larry Brasfield wrote: > If anybody truly cares enough to make this behave better, it is > encapsulated in a function named "booleanValue(char *zArg)". For > myself, since it takes "0" and "1", which are easy to type, the present >

Re: [sqlite] SQLite3 Bug Report: The shell accepts some dot commands ending in semicolons while rejecting others.

David Bicking wrote: Actually, it looks like anything except ".header on" will turn headers off. That includes ".header on;" (with semicolon - it doesn't do nothing, it turns the headers off) or ".header off;" (with or without semincolon.) or ".header ;" (with a space and semicolon but no

Re: [sqlite] SQLite3 Bug Report: The shell accepts some dot commands ending in semicolons while rejecting others.

From: Ryan Johnson To: sqlite-users@sqlite.org Sent: Monday, January 28, 2013 12:54 PM Subject: Re: [sqlite] SQLite3 Bug Report: The shell accepts some dot commands ending in semicolons while rejecting others. On 28/01/2013

Re: [sqlite] SQLite3 Bug Report: The shell accepts some dot commands ending in semicolons while rejecting others.

On 28/01/2013 12:08 PM, Larry Brasfield wrote: Nathan Chung wrote: SQLite version: 3.6.12 OS: Mac OS X 10.6.8 *Summary: The SQLite3 shell accepts some dot commands ending in semicolons while rejecting others without displaying proper error messages. The behavior of the dot commands could be

Re: [sqlite] SQLite3 Bug Report: The shell accepts some dot commands ending in semicolons while rejecting others.

Nathan Chung wrote: SQLite version: 3.6.12 OS: Mac OS X 10.6.8 *Summary: The SQLite3 shell accepts some dot commands ending in semicolons while rejecting others without displaying proper error messages. The behavior of the dot commands could be more consistent. Examples include "header off;"

Re: [sqlite] system.data.sqlite example code?

>From this URL http://www.dreamincode.net/forums/topic/157830-using-sqlite-with-c%23/ The basics of how to set your project and include/reference the Dlls are there. You should be able to adapt to your IDE. (I currently use VS2010 for C# sqlite projects.) and this one

Re: [sqlite] Use of sqlite as a FIFO buffer

Alexandros Kostopoulos wrote: > I would like to use sqlite as a FIFO buffer. In SQLite, tables are stored as a B-tree (indexed by the ROWID, or by the INTEGER PRIMARY KEY if you have declared one). When you remove the oldest entry, you get a hole in the first page of the table. When you add a

Re: [sqlite] bug report: out of memory error for most operations on a large database

On Sun, Jan 27, 2013 at 2:57 PM, ammon_lymphater < ammon_lympha...@hotmail.com> wrote: > > I think I localized the bug - potential query memory use with larger cache > sizes > > Details > - created a database and started in a loop 10 times { import 1m > records; run query} > - for

[sqlite] Use of sqlite as a FIFO buffer

I would like to use sqlite as a FIFO buffer. I know this isn't its intended use, but I a) need its robust storage backend and b) also need to apply and queries to it (so, it will not be actually used only as a FIFO). My questions are the following: - How would sqlite scale as a FIFO buffer

[sqlite] SQLite3 Bug Report: The shell accepts some dot commands ending in semicolons while rejecting others.

SQLite version: 3.6.12 OS: Mac OS X 10.6.8 *Summary: The SQLite3 shell accepts some dot commands ending in semicolons while rejecting others without displaying proper error messages. The behavior of the dot commands could be more consistent. Examples include "header off;" and "header on;". The

Re: [sqlite] bug report: out of memory error for most operations on a large database

I think I localized the bug - potential query memory use with larger cache sizes Details - created a database and started in a loop 10 times { import 1m records; run query} - for each iteration observe the memory use by SQLITE3 process using task manager - the mimimum use

Re: [sqlite] [sqlite-dev] Can I safely use the pragma synchronization = OFF?

TL;DR: If you want ACID at the OS and storage firmware level, expect to buy expensive server-rated hardware and expect it to be slow. On 28 Jan 2013, at 12:30pm, Phil Schwan wrote: > Arguably more importantly, there's an OS page cache that sits between your > application

Re: [sqlite] [sqlite-dev] Can I safely use the pragma synchronization = OFF?

I'm not even sure why I'm wading into this; glutton for punishment, I guess. TL;DR: the assumption that a data-journaled file system guarantees the atomicity of individual write()s is, in my experience, not a valid one. Unfortunately this isn't really a topic about which one can draw general

Re: [sqlite] [sqlite-dev] Can I safely use the pragma synchronization = OFF?

On Sun, Jan 27, 2013 at 12:21 PM, Shuki Sasson wrote: > No confusion here, the atomicity of the FS journal guarantees that the > fwrite will happen in full or not happen at all... > First off, SQLite uses write(), not fwrite(). Secondly, I don't think any modern unix-like

Re: [sqlite] [sqlite-dev] Can I safely use the pragma synchronization = OFF?

UFS is not fully journaled FS it jut keeps the metadata. With fully journaled File System that keeps metadata and data there is no possibility to loose unsaved data. Anything that was handed to fwrite and fwrite returned an OK for it is backed by the journal. Read the following: