diff --git a/Server/Migrations/01000001_AddHallOfFameColumns.cs b/Server/Migrations/01000001_AddHallOfFameColumns.cs index 34f8349..3956fc5 100644 --- a/Server/Migrations/01000001_AddHallOfFameColumns.cs +++ b/Server/Migrations/01000001_AddHallOfFameColumns.cs @@ -19,85 +19,38 @@ namespace SZUAbsolventenverein.Module.HallOfFame.Migrations { var entityBuilder = new HallOfFameEntityBuilder(migrationBuilder, ActiveDatabase); - // Add new columns manually since we are upgrading an existing table - // Note: Integer columns are generated as default/nullable depending on definition, Oqtane Helpers handle generic types. - // Using logic similar to Oqtane.Migrations.EntityBuilders - - if (ActiveDatabase.Name == "Sqlite") // Sqlite specific or generic - { - // Generic AddColumn: Table, Name, Type, Nullable - // However, Oqtane EntityBuilder usually builds tables. - // We will use migrationBuilder directly via helper if possible or standard AddColumn. + migrationBuilder.AddColumn( + name: "Year", + table: "SZUAbsolventenvereinHallOfFame", + nullable: false, + defaultValue: 0); + + migrationBuilder.AddColumn( + name: "Description", + table: "SZUAbsolventenvereinHallOfFame", + nullable: true); - migrationBuilder.AddColumn( - name: "Year", - table: "SZUAbsolventenvereinHallOfFame", - nullable: false, - defaultValue: 0); + migrationBuilder.AddColumn( + name: "Image", + table: "SZUAbsolventenvereinHallOfFame", + nullable: true); - migrationBuilder.AddColumn( - name: "Description", - table: "SZUAbsolventenvereinHallOfFame", - nullable: true); // Allow nulls initially or empty? MaxString usually nullable in Oqtane context? Let's check. - - migrationBuilder.AddColumn( - name: "Image", - table: "SZUAbsolventenvereinHallOfFame", - nullable: true); + migrationBuilder.AddColumn( + name: "Link", + table: "SZUAbsolventenvereinHallOfFame", + nullable: true); - migrationBuilder.AddColumn( - name: "Link", - table: "SZUAbsolventenvereinHallOfFame", - nullable: true); + migrationBuilder.AddColumn( + name: "Status", + table: "SZUAbsolventenvereinHallOfFame", + maxLength: 50, + nullable: true); - migrationBuilder.AddColumn( - name: "Status", - table: "SZUAbsolventenvereinHallOfFame", - maxLength: 50, - nullable: true); - - migrationBuilder.AddColumn( - name: "UserId", - table: "SZUAbsolventenvereinHallOfFame", - nullable: false, - defaultValue: 0); - } - else - { - // For SQL Server / others, simply use same AddColumn but allow EF Core to handle types - migrationBuilder.AddColumn( - name: "Year", - table: "SZUAbsolventenvereinHallOfFame", - nullable: false, - defaultValue: 0); - - migrationBuilder.AddColumn( - name: "Description", - table: "SZUAbsolventenvereinHallOfFame", - nullable: true); - - migrationBuilder.AddColumn( - name: "Image", - table: "SZUAbsolventenvereinHallOfFame", - nullable: true); - - migrationBuilder.AddColumn( - name: "Link", - table: "SZUAbsolventenvereinHallOfFame", - nullable: true); - - migrationBuilder.AddColumn( - name: "Status", - table: "SZUAbsolventenvereinHallOfFame", - maxLength: 50, - nullable: true); - - migrationBuilder.AddColumn( - name: "UserId", - table: "SZUAbsolventenvereinHallOfFame", - nullable: false, - defaultValue: 0); - } + migrationBuilder.AddColumn( + name: "UserId", + table: "SZUAbsolventenvereinHallOfFame", + nullable: false, + defaultValue: 0); } protected override void Down(MigrationBuilder migrationBuilder)