[Buildbot-devel] the aftermath (was Re: SF bay area get-together?)

Robert Helmer robert at roberthelmer.com
Sun Jul 27 19:47:07 UTC 2008

On Sat, Jul 26, 2008 at 4:14 AM, Axel Hecht <l10n.moz at googlemail.com> wrote:

> 2008/7/25 john gale <john at smadness.com>:
> >
> > On Jul 25, 2008, at 1:17 PM, Robert Helmer wrote:
> >
> >> * using sqlite as backend (instead of current pickle-to-file method)
> >
> >
> >
> > As discussed last night, I think lots of projects can get started as
> > soon as the build result data is in sqlite.  Custom UI front ends can
> > then be written (for the management "green light" / "red light"
> > problem) very easily (and in our choice of language :)
> >
> I'd suggest to not lock ourselves in to sqlite. While that's cool for
> smaller projects, and in order to be able to just start things up, I'd
> rather have the choice to separate the master from the db. Like, one
> of the reasons to not use the web display of the master is to protect
> the precious one from external evil doers. Having a way to access the
> database remotely is one way to do that. Not to mention that one could
> drop in something more scalable if required.

This was discussed too! I neglected to mention, sorry.

What are good practical ways to do this separation? I've been playing with
SQLAlchemy lately and it seems quite good, hopefully others have more
real-world experience though.. seems like you can take-or-leave a lot of the
ORM stuff, I am hoping to use it to abstract some of the database
differences so I don't have to have a ton of custom SQL for each major

Also, Twisted has an RDBMS connector, I guess most DB APIs are blocking so
they won't really work well with Twisted:


I don't think this would help with regard to writing a ton of custom SQL,
this just gets you to the DB-API.

Axiom provides an ORM layer but looks like it only supports SQLite and no
concurrency to date.

As far as I can tell from some quick Google searches, the only viable way to
do this today is to use Twisted's RDBMS and have your Twisted app explicitly
support each database, which doesn't sound like a ton of fun :)

If that's the case, SQLite seems like a good place to start at least. Like I
said though, hopefully others can school me on this, and it's not so bleak
as I've made out :P
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20080727/dc10445b/attachment.html>

More information about the devel mailing list