On Wed, Jul 30, 2008 at 1:27 PM, Chris Hyzer <[EMAIL PROTECTED]> wrote: > Hey, > When the script copies data to another table, and back, should it not commit > after each step? The reason is if the transaction fails or is rolled back > after the table ddl has occurred, there will be data loss, right?
Databases usually don't support transactional DDL, which means that a DDL statement will commit all currently open transactions for that session. In any case, DdlUtils currently assumes the connection to be auto-commit (i.e. it does no explicit transaction) - this is configurable via the data source. But feel to file an enhancement JIRA to make DdlUtils insert COMMIT SQL into the generated SQL. Tom
