marplatense/sqla_hierarchy — pull request #2 by zzzeek (2012-08-31 14:49:42+00:00)
Title: fix test config so that backends are optional

hello there -

I've been tasked with debugging a sqla_hierarchy issue present at http://www.sqlalchemy.org/trac/ticket/2558. I don't know the nature of the issue yet but I see that sqla_hierarchy makes elaborate use of SQLA expression constructs, so it's very likely I'll need to modify sqla_hierarchy to be compatible with upcoming SQLAlchemy releases (including 0.7.9). To that end I can easily add sqla_hierarchy to a new Jenkins environment I've been building (see http://jenkins-stage.sqlalchemy.org/) however the build system for sqla_hierarchy needs to be more agile. This pull request establishes each database config as optional, emitting SkipTest for those platforms not installed. We have separate build nodes for Oracle and PG, basically.