Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: How to perform Identity Inserts when inserting an entity? #1135

Open
pmarflee opened this issue Mar 8, 2023 · 2 comments
Open
Assignees
Labels
question Further information is requested

Comments

@pmarflee
Copy link

pmarflee commented Mar 8, 2023

I understand that RepoDB does not natively support the SQL Server SET IDENTITY_INSERT ON | OFF operation because it is vendor-specific. However, if I have manually enabled Identity Insert on the current connection, how can I actually set the identity value when inserting an entity into my SQL Server database? I'm getting the following error when performing the insert:

Microsoft.Data.SqlClient.SqlException
  HResult=0x80131904
  Message=Explicit value must be specified for identity column in table '<TableName>' either when IDENTITY_INSERT is set to ON or when a replication user is inserting into a NOT FOR REPLICATION identity column.
  Source=Core Microsoft SqlClient Data Provider

I can see that RepoDB runs a query to obtain the column metadata the first time an entity is used. One of the metadata values returned by this query is 'IsIdentity'. I'm guessing that this metadata value is then used to determine whether an explicit value for a field should be included in the INSERT statement sent to the database.

Is there a way to tell RepoDB to override the default behaviour for a specific operation and allow identity inserts?

@pmarflee pmarflee added the question Further information is requested label Mar 8, 2023
@mikependon
Copy link
Owner

Hmmmm... A very interesting question. First, RepoDB does not understand that the underlying database IDENTITY INSERT setting has been turned ON/OFF. As RepoDB is eliminating the column in the push operations (Insert, Merge) if it is set as identity in the table, it therefore triggers that problem.

Have you tried inserting via anonymous types?

Let us say you have table like below.

CREATE TALBE [schema].[Table]
(
    [Id] INT PRIMARY IDENTITY (1, 1),
    [Name] NVARCHAR(256),
    [Description] NVARCHAR(MAX)
);

Then, you can insert all the data using the code below. (Without using any class model)

using (var connection = new SqlConnection(connectionString))
{
     connection.ExecuteNonQuery("SET IDENTITY_INSERT [schema].[Table] ON;");
     var entities = GetEntitiesAsAnonymousTypes();
     connection.InsertAll("[schema].[Table]", entities);
     connection.ExecuteNonQuery("SET IDENTITY_INSERT [schema].[Table] OFF;");
}

In which the method GetEntitiesAsAnonymousTypes() returns the list of entities as anonymous types.

public List<EntityModel> GetEntitiesAsAnonymousTypes()
{
     for (var i = 0; i <= 100; i  )
     {
          yield return new { Id = (i   1), Name = "Name", Description = "Description };
     }
}

Note: The code above is adhocly written and is not tested, but it should work if corrected any wrong typos.

@mikependon mikependon self-assigned this Mar 16, 2023
@pmarflee
Copy link
Author

pmarflee commented Mar 16, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants