[zz]schema manager

http://kered.org/blog/2006-05-24/summer-of-code/

Additionally, it supports the following:

automatic downgrades are supported (in addition to upgrades)
the application can automatically identify a schema without a ’schema version’ table
the application can verify the accuracy of a schema
multiple schema identification algorithms are simultaneously supported (for instance: primary keys, foreign keys and constraints can be named in Oracle – should a constraint name change be considered a schema version change? you decide)
multiple different schemas with ‘equivalent’ functionality can be mapped back to a single logical schema version (’equivalency’ obviously being determined by the developer)

评论

1 楼 iunknown 2009-07-09  

http://almaer.com/blog/the-new-attack-on-the-rdbms

SQL is just incredibly powerful as a query language. Nothing has ever come close. OO querying (as in hibernate) is just unreadable and unwritable and not nearly as powerful as SQL.

The main problems with RDBMs have to do not with SQL, but with the schema. Creating a schema, foreign keys, etc. is a pain. Changing it is a pain. Add to that the corporate policy that goes with changing such schemas and forget about it.

Elimination of the schema, or simplification of it’s creation should be the goal.