What steps will reproduce the problem?
1. Create a migration that creates multiple tables in an Oracle schema,
and one of the tables cannot be created
What is the expected output? What do you see instead?
I expect that none of the tables in the migration exists in the database
schema. I expect to be able to run the migration after the error in one of
the tables is fixed.
Instead, some of the tables created as part of the migration remain in the
database schema, which prevents to re-run the migration (you encounter
errors because database objects like tables and/or foreign keys already
exist).
What version of the product are you using?
migratordotnet.0.8.0
On what operating system?
Windows XP
With what .NET implementation/version?
.NET 3.5
What database and version are you seeing this issue on?
Oracle 10.2
Please provide any additional information below.
In SQL Server the DDL statements are rolled back, on Oracle they are not.
I suspect that the DDL statements are wrapped inside a transaction, but on
Oracle schema changes cannot be reverted by rolling back the transaction
(this only applies to DML statements). So for Oracle, the reverse DLL
statements should be executed (e.g. DROP TABLE ...).
Original issue reported on code.google.com by paul.dhe...@gmail.com on 27 May 2009 at 7:12
Original issue reported on code.google.com by
paul.dhe...@gmail.comon 27 May 2009 at 7:12