Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Oracle migrations are not transactional by default

See original GitHub issue

Describe the bug If I run migrations on oracle db and after some error happen I clearly see there are partially some tables crated. I cannot see it in mssql. Migrations Table is created and it is empty.

To Reproduce Create a migrator with some table creation and then add next line which will throw an error. You will see that the first table is created.

Expected behavior It should rollback whole transaction without creating anything.

Information (please complete the following information):

OS: Windows 10
Platform .NET Core 3.1.x
FluentMigrator version 3.2.6
FluentMigrator runner
Database Management System: Oracle
Database Management System Version: “Oracle 18xe”

Additional context

    [Migration(201909232030)]
    public class MIG_20190923_2030_Init : Migration
    {
        public override void Up()
        {
            ...

Issue Analytics

State:
Created 3 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

jzabroskicommented, Jun 4, 2020

No worries. Oracle shops tend to use the Down part of migrations a lot 😃

0reactions

jzabroskicommented, Jun 4, 2020

I think somewhere in the backlog I started spec’ing out something for restoring data as part of migrations, but I can’t even recall my thought process at the time. I think it involved copying all the related data to a separate schema and transfering it back, which would be a minimal t-log operation in case of rollback required.