Hi folks.
I'm gradually hacking my Openguide installation into shape, getting some starter content in there. I'll start pushing it more publicly when I'm happy with it and think it's ready for the big bad world (and slashdotting, which is probably inevitable)
Here's the (current) URL. I'll ask for an openguides subdomain when I work out what I want to call it. Comments gratefully received. http://stout.rumble.net/cgi-bin/openguides/wiki.cgi
Now my question is this: how well does sqlite as my database scale? What are the caveats? According to the web site it is ACID and thus a "real" database (thought the "C" is kinda laughable since it doesn't enforce foreign key constraints).
What do I need to do if I decide to upgrade to a "real" RDBMS? Is it easy to move the data from one to the other?
On Wed, Oct 06, 2004 at 11:18:46AM +0100, Rev Simon Rumble wrote:
Now my question is this: how well does sqlite as my database scale?
For the craziness I'm doing with email, one of my sqlite tables had hundreds of thousands of records. It worked. I have, however, migrated it to Sybase.
What are the caveats? According to the web site it is ACID and thus a "real" database (thought the "C" is kinda laughable since it doesn't enforce foreign key constraints).
It's not as fast as (eg) Sybase for what I want to do, partly I think because SQLite has no concept of data types, and so doesn't treat ints (which is what I mostly search on) in the most efficient manner.
What do I need to do if I decide to upgrade to a "real" RDBMS? Is it easy to move the data from one to the other?
I'd define the tables in the new db but without foreign key constraints or indices; then for each table, select all the rows from the sqlite db and insert into the new one; finally, turn the constraints and indices on
The usual caveats about SQL dialects and portability apply, of course.
On Wed, Oct 06, 2004 at 12:48:57PM +0100, David Cantrell wrote:
I'd define the tables in the new db but without foreign key constraints or indices; then for each table, select all the rows from the sqlite db and insert into the new one; finally, turn the constraints and indices on
The usual caveats about SQL dialects and portability apply, of course.
It would be really excellent if someone could write a set of scripts for doing this for CGI::Wiki databases and this script could be included in CGI::Wiki.
Cheers,
Dominic.
On Wed, 6 Oct 2004 12:48:57 +0100, David Cantrell david@cantrell.org.uk wrote:
It's not as fast as (eg) Sybase for what I want to do, partly I think because SQLite has no concept of data types, and so doesn't treat ints (which is what I mostly search on) in the most efficient manner.
I too just discovered that SQLite is not a replacement for a proper database. I wanted to use it as a replacement for some temporary tables put into a Sybase database. Unfortunately SQLite was unable to do the same maths as Sybase and I got the wrong answers. Will that matter for an OpenGuides installation? I don't really know.
This doesn't really help answer the question "Does SQLite scale?" but it may push the original poster towards using a proper RDBMs rather than SQLite.
Alex
This one time, at band camp, Alex McLintock wrote:
I too just discovered that SQLite is not a replacement for a proper database. I wanted to use it as a replacement for some temporary tables put into a Sybase database. Unfortunately SQLite was unable to do the same maths as Sybase and I got the wrong answers. Will that matter for an OpenGuides installation? I don't really know.
There is something in the sqlite FAQ about its treatment of 00 type strings as zero.
openguides-dev@lists.openguides.org
-
Alex McLintock -
David Cantrell -
Dominic Hargreaves -
Rev Simon Rumble