Some platforms do not have support for transactional DDL (rumor has it that
Oracle wraps each DDL statement in a separate transaction). This breaks the
whole transactional flow Wizardby expects to be in place.
This has to be somehow resolved so that all upgrade/downgrade commands will
work as expected. First idea is to add a separate SchemaInfoSignature tableso
that it will contain a hash of each DDL statement executed against a database
for a particular version.
Original issue reported on code.google.com by anton.go...@gmail.com on 22 Jan 2010 at 8:28
Original issue reported on code.google.com by
anton.go...@gmail.com
on 22 Jan 2010 at 8:28