Now I have, in python, created a class which does only the things I need to at begin with the first database part of Unified BPM, creating and querying simple database structures.
The class can currently create these kinds of SQL statements(and then some):
- SELECT - with where, expressions, conditions, CASE, function calls, joins, subselects.
- CREATE TABLE - with defaults, primary keys, foreign keys and autoincrement
- CREATE INDEX - Unique, Clustered, Non-Clustered
- SQL Server
- Partial DDL
- Oracle(due to identifier limitations and auto-increment hassle)
I now have working installations of all five databaseservers and will use them to set up integration tests for all flavours.
In practice, Partial DDL means that Unified BPM won't run on that platform but will be able to communicate with it. I simply won't commit to restricting myself to 30 bytes long identifiers. Somebody please think of the FK-names!