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 possibility of extracting the necessary tables/columns
into SQLite at a regular interval and running Crystal against that instead.
At the moment I've using Perl to build and then tear down the temporary
SQLite database, to dynamically create SQL script files that INSERT the
necessary data, and to load the SQL scripts into SQLite via the command
line, e.g.
sqlite3 temp.db ".read create.load"
create.load is actually the first script which just contains:
PRAGMA default_cache_size=250000;
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');
The timestamp table allows me to crudely check when the extract-load
process last ran, and it also makes sure that by the time this script
finishes the SQLite database is in place. My problem is that of the two
optimisation pragmas, default_cache_size appears to be working but not
page_size. When I check the latter after the script has completed it is
still 1024 bytes.
I thought that provided you hadn't created any tables the page_size
setting should work. Can anybody duplicate this issue or point out my
spot-the-newbie mistake?
Thanks
--
Neil Hughes
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
