Difficulty extending NpgsqlMigrationSqlGenerator

The SQL generation for AlterColumn cannot easily be extended. In order to add USING "Id"::uuid I'd have to re-implement all the logic in Convert(AlterColumnOperation alterColumnOperation) and all the internal members called from that method:

EntityFramework6.Npgsql/EF6.PG/NpgsqlMigrationSqlGenerator.cs

Lines 244 to 247 in 55c1900

    
           AppendAlterColumn(alterColumnOperation, sql); 
        
           sql.Append(" TYPE "); 
        
           AppendColumnType(alterColumnOperation.Column, sql, false); 
        
           AddStatment(sql);

. Ideally those methods would be open to extension / some other hooks to easily add a USING statement.

E.g. I'd need to change:

ALTER TABLE "public"."Entity" ALTER COLUMN "Id" TYPE uuid

into this:

ALTER TABLE "public"."Entity" ALTER COLUMN "Id" TYPE uuid USING "Id"::uuid

I've now worked around this by overriding the generated sql:

public override IEnumerable<MigrationStatement> Generate(IEnumerable<MigrationOperation> migrationOperations, string providerManifestToken)
{
    foreach (var statement in base.Generate(migrationOperations, providerManifestToken))
    {
        var match = Regex.Match(statement.Sql, "ALTER TABLE .*? ALTER COLUMN (?<column>.+?) TYPE uuid");
        if (match.Success)
            statement.Sql += $" USING {match.Groups["column"]}::uuid";
        yield return statement;
    }
}

Hmm. Is this something a EF6 provider should be able to to handle? Shouldn't the EF itself have support for this first? I mean can this be fixed? Note that the new EF Core is far more flexible than the ancient EF6.

Yeah, I doubt the EF6 provider model gives a lot of flexibility here. As @Emill mentions, EF Core was designed from the start with this kind of extensibility in mind. In any case, this provider is pretty much archived at this point - although we'd accept well-written PRs for bug fixes, realistically speaking it's not going to evolve, e.g. by introducing new hooks. So I'm going to go ahead and close this for now (but feel free to post back here of course).

I do believe the provider model gives that flexibility, but the implementation of NpgsqlMigrationSqlGenerator is too closed. I can, for example override protected virtual void Convert(AlterColumnOperation alterColumnOperation), but I cannot override any of the methods it's calling. Also this method doesn't have a return value that I can replace in a subclass, and the result aggregation also happens through a method I cannot extend:void AddStatment(string sql, bool suppressTransacion = false).

I understand the EOL decision on this package, and as I have workaround my immediate need is taken care of.

	AppendAlterColumn(alterColumnOperation, sql);
	sql.Append(" TYPE ");
	AppendColumnType(alterColumnOperation.Column, sql, false);
	AddStatment(sql);