Re: Re: [PyCS-devel] Re: Maybe problems with Metakit 2.4.9.3

> You might consider SQLite. I've never used it so I can't recommend it 
> per se, but it is closer to Metakit in that you can open files yourself 
> for databases, rather than having to use the system DB.
> 
> (I would imagine PyCS would still want MySQL or Postgres, truthfully, 
> but it is worth a look. PyDS might be a better fit with SQLite. I *like* 
> being able to backup my PyDS just by shutting it down and copying some 
> files. I think SQLite should retain that, it isn't so easy for MySQL.)

Good idea.  Do you know what SQLite's memory consumption is like?  I'm
not happy with the amount of memory my PyCS processes are using up at
the moment on my server, and suspect that MK has a lot to do with it.

Here are my reasons for switching:

- MK uses too much memory.

- MK is single user; I can't play with the DB without shutting down
PyCS.  [it looks like SQLite might let me do this too].

- I don't trust MK not to lose data.

- The MK file is hard to inspect - I have to either download it onto
another machine or write code to access it.

If I can get rid of these problems using SQLite, then it would
probably be a better choice than MySQL or Postgres as you still
wouldn't need to install a separate DB to get PyCS running.

Cheers,
Phil