[Systers-dev] Database Schema for Message Storing

Yian Shang yian.shang at gmail.com
Sun Jul 25 03:24:10 PDT 2010


On Sun, Jul 25, 2010 at 3:04 AM, Anna Granudd <anna.granudd at gmail.com>wrote:

> Sorry if it's a really stupid question (I've been following the messages in
> this thread but I don't know enough about databases to really understand
> everything concerning the discussions about MongoDB etc.) but does this mean
> we're implementing a new db, possibly no longer PostgreSQL? If so, it might
> be a good idea to use SQLite since that's what Mailman 3 uses (and it's what
> I've been using for the models in the UI, although that we can easily
> change) and the consistency would probably make things easier for us if
> we're thinking of changing the DB anyways. Just an idea, maybe I got it all
> wrong and then I apologize.
>

Actually, currently the db is still PostgreSQL (I was following along what
was being used for dlist-storing), and it's just for storing messages (it
basically replaces mbox files). I didn't realize that Mailman 3 was using
SQLite; it would be more consistent to go along with that. And I think the
fact that it's so hard to decide exactly which database to use is good
reason for the abstraction--if we eventually want to try out some new one
it'd be easier to do so (hopefully!).


> Cheers,
> Anna
>

Yian

To contribute to this conversation, send mail to <Anna Granudd >


More information about the Systers-dev mailing list