migratordotnet / migrator.net Goto Github PK

Unexpected behavior when using schema.
For instance:
Assert.IsTrue(_provider.ColumnExists("dbo.TestTwo", "TestWithDefault"));
Will fail even if the column is present in the table.

If the .csproj is modified so that it calls Migrate task in the AfterBuild target the project DLL will stay locked after the first compile. The problem is that Assembly.LoadFrom locks the DLL and it can not be unloaded.

Solution for the problem is adding the attributes [LoadInSeparateAppDomain] and [Serializable] to the Migrator.MSBuild.Migrate class and inheriting from AppDomainIsolatedTask instead of the Task. TaskLogger has to be change accordingly.

[LoadInSeparateAppDomain]
[Serializable]
public class Migrate : AppDomainIsolatedTask 
{ 

 public class TaskLogger : ILogger
{
    private readonly AppDomainIsolatedTask _task;

    public TaskLogger(AppDomainIsolatedTask task)
           {
                   _task = task;
           }

Sorry for not using the GIT :(

E.g. when we have just one migration and issue a command to migrate to version 2 on the command line:

Migrator.Console.exe SqlServer "Data Source=..." Database.dll -version 2

the application wil go forever:

2 <Migration not found>
2 <Migration not found>
2 <Migration not found>
2 <Migration not found>
2 <Migration not found>
2 <Migration not found>
...

Hi,

When I try to create a table with a GUID type for the ID, I get an exception that GUIDs are not allowed. (This is with the SQL Server provider.)

I'm sure there's a reason for this. The problem is, I'm creating a JSON API, so I need GUIDs for everything -- I don't want to manage a pair of IDs (integer for the DB and GUID for everything else).

Is there a way around this? SQL Server itself allows GUID primary keys.

Edit: This error doesn't appear to be coming from Migrator.NET. It's because I specified PrimaryKeyWithIdentity. Changing it to PrimaryKey works.

Currently the BeginTransaction method in TransformationProvider always uses IsolationLevel.ReadCommitted to begin the transaction. In MySQL 5.1.66 if you are using InnoDB tables and Statement based replication the isolation level must be either IsolationLevel.RepeatableRead or IsolationLevel.Serializable.

Could the TransformationProvider be updated so that the isolation level was configurable via a property? Or as a argument to the BeginTransaction method?