Hello viswajwalith,
Please do let us know if we can help you with something else?
Can we close this ticket if your query is resolved? Please Confirm.
Thank You, Anjali
For for delay in the response, actually we upgraded directly from 5.1.3 to 7.3.2 and seems working. but not 100% tested. for now you can close the ticket will let you know in case of any queries/concerns.
Actually we followed different approach will let you know in a day or two. Thanks for response.
Hi viswajwalith,
We are checking, will update you asap.
Thanks for the confirmation
Hi Any update on this this by chance?
hi
I think you can only use the
dotnet ef migrations script
to get the script on each project.The migratory tool just applies the migration and seeds the data.
That's fine, we will generate manually for DB structural changes. but do we have any other way to generate the insert scripts for data seeding from the Migration tool right? Mainly for Permission, Roles and Tenant specific data.
Also sometimes we are getting the Generated SQL file as empty, any idea on that? for the below code
using System;
using Microsoft.EntityFrameworkCore.Migrations;
#nullable disable
namespace XXXX.Migrations
{
public partial class ImportHistoryLogImportRunHistory : Migration
{
protected override void Up(MigrationBuilder migrationBuilder)
{
migrationBuilder.AddColumn<string>(
name: "CustomField1",
table: "EmployeeServiceImportRunHistories",
type: "nvarchar(max)",
nullable: true);
migrationBuilder.AddColumn<string>(
name: "CustomField2",
table: "EmployeeServiceImportRunHistories",
type: "nvarchar(max)",
nullable: true);
migrationBuilder.AddColumn<string>(
name: "CustomField3",
table: "EmployeeServiceImportRunHistories",
type: "nvarchar(max)",
nullable: true);
migrationBuilder.AddColumn<string>(
name: "CustomField4",
table: "EmployeeServiceImportRunHistories",
type: "nvarchar(max)",
nullable: true);
migrationBuilder.AddColumn<string>(
name: "CustomField5",
table: "EmployeeServiceImportRunHistories",
type: "nvarchar(max)",
nullable: true);
migrationBuilder.AddColumn<string>(
name: "RowNo",
table: "EmployeeServiceImportRunHistories",
type: "nvarchar(max)",
nullable: true);
migrationBuilder.AddColumn<string>(
name: "CustomField1",
table: "EmployeeServiceImportHistroyLogs",
type: "nvarchar(max)",
nullable: true);
migrationBuilder.AddColumn<string>(
name: "CustomField2",
table: "EmployeeServiceImportHistroyLogs",
type: "nvarchar(max)",
nullable: true);
migrationBuilder.AddColumn<string>(
name: "CustomField3",
table: "EmployeeServiceImportHistroyLogs",
type: "nvarchar(max)",
nullable: true);
migrationBuilder.AddColumn<string>(
name: "CustomField4",
table: "EmployeeServiceImportHistroyLogs",
type: "nvarchar(max)",
nullable: true);
migrationBuilder.AddColumn<string>(
name: "CustomField5",
table: "EmployeeServiceImportHistroyLogs",
type: "nvarchar(max)",
nullable: true);
migrationBuilder.AddColumn<string>(
name: "RowNo",
table: "EmployeeServiceImportHistroyLogs",
type: "nvarchar(max)",
nullable: true);
}
protected override void Down(MigrationBuilder migrationBuilder)
{
migrationBuilder.DropColumn(
name: "CustomField1",
table: "EmployeeServiceImportRunHistories");
migrationBuilder.DropColumn(
name: "CustomField2",
table: "EmployeeServiceImportRunHistories");
migrationBuilder.DropColumn(
name: "CustomField3",
table: "EmployeeServiceImportRunHistories");
migrationBuilder.DropColumn(
name: "CustomField4",
table: "EmployeeServiceImportRunHistories");
migrationBuilder.DropColumn(
name: "CustomField5",
table: "EmployeeServiceImportRunHistories");
migrationBuilder.DropColumn(
name: "RowNo",
table: "EmployeeServiceImportRunHistories");
migrationBuilder.DropColumn(
name: "CustomField1",
table: "EmployeeServiceImportHistroyLogs");
migrationBuilder.DropColumn(
name: "CustomField2",
table: "EmployeeServiceImportHistroyLogs");
migrationBuilder.DropColumn(
name: "CustomField3",
table: "EmployeeServiceImportHistroyLogs");
migrationBuilder.DropColumn(
name: "CustomField4",
table: "EmployeeServiceImportHistroyLogs");
migrationBuilder.DropColumn(
name: "CustomField5",
table: "EmployeeServiceImportHistroyLogs");
migrationBuilder.DropColumn(
name: "RowNo",
table: "EmployeeServiceImportHistroyLogs");
}
}
}
Thanks
We are still preparing the sample solutions, will share by tomorrow max
hi
We don't familiar with MongoDB, You can create a sample project with ef core.
We will try to provide a sample in two days to continue our discussion.