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

Jean-Paul Calderone exarkun at divmod.com
Sun Jul 27 21:00:53 UTC 2008

On Sun, 27 Jul 2008 12:47:07 -0700, Robert Helmer <robert at roberthelmer.com> wrote:
> [snip]
>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

I expect buildbot's requirements are fairly simple.  What is necessary
beyond inserting rows representing newly available results?

For this level of use, it's easy to write SQL that will work with all
major RDBMS.


More information about the devel mailing list