Re: AW: Big, BIG databases.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

| as I type this that it might be easier to start out with a Post object
| and then work on abstracting the storage, rather than the other way
| around as I tried before.

My plans on this up to now were to use SQLObject and SQLite as a
replacement of Metakit. Of course it would require to change the overall
structure of PyDS, as Metakit isn't abstracted away currently. Maybe
some base ideas on PyDS:

- - tools should be mostly independend on one another, at least highlevel
tools like wiki, weblog, pictures etc. - this includes their databases,
they should have their own "tablespace" to work with.

- - tools should use stuff from other tools via the getTool() call and
then accessing member functions of the returned instance. They should
never directly access database stuff from other tools but allways go
through member functions.

- - tools should provide hooks for other tools to "hook into" processing
(like some tools hooking into the rendertool or some others hooking into
the weblog). This should include database stuff: don't try to do one big
database schema to model the post class, just do a rather abstract and
barebones schema and add stuff by using the current way of tools hooking
into other tools and managing their own tables.

That's the way that PyDS is currently built and I think sticking to this
way of doing it would make the database layer switch easier. Maybe it
really would just be a good idea to use SQLObject exactly where
currently Metakit is used and look what needs to be changed. I didn't
use the subtable stuff from Metakit too often, so it's mostly simple
tables managed as a list of objects in Metakit - and that should match
quite fine to a list of objects managed by SQLObject.

We can abstract away the SQL stuff mostly by using SQLObject - what
would give us the nice sideeffect of not having to concentrate on one
database too much and would allow to start with SQLite but allow people
to "upgrade" to PostgreSQL if they have needs that go beyond SQLite.

bye, Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCLWiCF23K68kpzdoRAtvLAJ9rn7tU0nA7yRY62TXG8nnKXBaxRgCfftsj
B1PBsPLNHpW9WH68FguZiqw=
=cpCi
-----END PGP SIGNATURE-----