Joe Wilson wrote:
page_size must be the first statement.
PRAGMA page_size=4096;
PRAGMA default_cache_size=25;
Thanks Joein hindsight, that's something I should have checked, but
it never crossed my mind.
And thanks Andy for explaining the physical effect of default_cache_size
in a
On 6/27/07, Andrew Finkenstadt <[EMAIL PROTECTED]> wrote:
On 6/27/07, Neil Hughes <[EMAIL PROTECTED]> wrote:
>
> PRAGMA default_cache_size=25;
> PRAGMA page_size=4096;
> CREATE TABLE timestamp (date TEXT, time TEXT, script_version REAL);
> INSERT INTO timestamp VALUES('27/06/07', '14:38:18',
On 6/27/07, Neil Hughes <[EMAIL PROTECTED]> wrote:
PRAGMA default_cache_size=25;
PRAGMA page_size=4096;
CREATE TABLE timestamp (date TEXT, time TEXT, script_version REAL);
INSERT INTO timestamp VALUES('27/06/07', '14:38:18', '0.01');
I've only just learned this today during an "innocent"
page_size must be the first statement.
PRAGMA page_size=4096;
PRAGMA default_cache_size=25;
CREATE TABLE timestamp (date TEXT, time TEXT, script_version REAL);
INSERT INTO timestamp VALUES('27/06/07', '14:38:18', '0.01');
> sqlite3 temp.db ".read create.load"
>
> create.load is actually the
I've just started using SQLite 3 and I'm hoping to use it to solve an
issue I have with another DBMS - in short, a customer "upgraded" to
Crystal Enterprise and now some of their reports against a Pervasive.SQL
database no longer work due to a weird memory-leak-type issue. I'm
investigating the
5 matches
Mail list logo