Using HasData to seed an Entity with a mapped Enum creates a migration that errors with: PostgresException (0x80004005) 42703: column "{{enum value}}"

Offen
  • Stimmt etwas nicht?
#3,426 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
csharp, postgresql
Bereich
databases

Rechercherichtung

Start by reproducing the reported case: map the PostgreSQL enum and seed the entity with HasData, then generate and run the initial migration. Inspect the generated InsertData values for the enum. The issue is resolved when the migration runs successfully without treating the enum value as a column name.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Hi,

I think this is a minor bug on migration code generation, and while I found a work around, I thought I'd contribute my findings. I searched issues and didn't see anyone mention this yet.

Consider the below setup where Voice is an Entity model, and it has a reference to an enumeration, VoiceSource

An enumeration with Npgsql mapping added
public enum VoiceSource
{
    Recording = 0,
    Azure = 1,
}

opt.UseNpgsql(
        builder.Configuration.GetConnectionString("ZabaanDbContext"),
        o =>
        {
            o.MapEnum<VoiceSource>(nameof(VoiceSource));
            o.UseNodaTime();
        }
    );
I have some seed data configured:
public static readonly Voice Voices_AzureFarid = new Voice
{
    Id = VoiceId.AzureFarid, // vogen wrapped urn
    Source = VoiceSource.Azure,
    SourceIdentifier = "fa-IR-FaridNeural",
    Name = "Farid",
};

public static readonly Voice Voices_AzureDilara = new Voice
{
    Id = VoiceId.AzureDilara, // vogen wrapped urn
    Source = VoiceSource.Azure,
    SourceIdentifier = "fa-IR-DilaraNeural",
    Name = "Dilara",
};

modelBuilder.Entity<Voice>(voice =>
{
    voice.HasIndex(e => new { e.Source, SourceIdentifer = e.SourceIdentifier }).IsUnique();
    voice.HasIndex(e => e.Name).IsUnique();
    voice.HasData(Voices_AzureFarid, Voices_AzureDilara);
});
Then, when I make my INITIAL database migration, this code is generated where the enumeration is referenced directly:
migrationBuilder.InsertData(
    table: "Voices",
    columns: new[] { "Id", "Name", "Source", "SourceIdentifier" },
    values: new object[,]
    {
        { "urn:zabaan:voice:0a57108b-18d7-4877-ac09-67d73150da08", "Dilara", VoiceSource.Azure, "fa-IR-DilaraNeural" },
        { "urn:zabaan:voice:d0d96aa5-971b-4d78-a606-471469663c34", "Farid", VoiceSource.Azure, "fa-IR-FaridNeural" }
    });
Which fails to run via the migration bundle application:
INSERT INTO "Voices" ("Id", "Name", "Source", "SourceIdentifer")
VALUES ('urn:zabaan:voice:d0d96aa5-971b-4d78-a606-471469663c34', 'Farid', Azure, 'fa-IR-FaridNeural');
Npgsql.PostgresException (0x80004005): 42703: column "azure" does not exist
The fix

Updating the migration file manually to use the string value wrapped with single quotes fixed the issue and the migration succeeds:

migrationBuilder.InsertData(
    table: "Voices",
    columns: new[] { "Id", "Name", "Source", "SourceIdentifier" },
    values: new object[,]
    {
        { "urn:zabaan:voice:0a57108b-18d7-4877-ac09-67d73150da08", "Dilara", "\'azure\'", "fa-IR-DilaraNeural" },
        { "urn:zabaan:voice:d0d96aa5-971b-4d78-a606-471469663c34", "Farid", "\'azure\'" , "fa-IR-FaridNeural" }
    });

The single quotes wrapping the "azure" are necessary FYI, I first tried it without and that also failed.

Failed executing DbCommand (56ms) [Parameters=[], CommandType='Text', CommandTimeout='30']
INSERT INTO "Voices" ("Id", "Name", "Source", "SourceIdentifer")
VALUES ('urn:zabaan:voice:0a57108b-18d7-4877-ac09-67d73150da04', 'Dilara', azure, 'fa-IR-DilaraNeural');
INSERT INTO "Voices" ("Id", "Name", "Source", "SourceIdentifer")
VALUES ('urn:zabaan:voice:d0d96aa5-971b-4d78-a606-471469663c38', 'Farid', azure, 'fa-IR-FaridNeural');
Npgsql.PostgresException (0x80004005): 42703: column "azure" does not exist
Vorherrschende Sprache
C#
Sterne
1.8k
Forks
268
Ø Merge
2 Std. 35 Min.
Gemergte PRs (30 T.)
136

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus npgsql/efcore.pg

Alle Issues in npgsql/efcore.pg

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.