AutoMapOutputIdentity not working with Microsoft.Data.Sqlite

[BEagle1984]

AutoMapOutputIdentity not working with Microsoft.Data.Sqlite

[JonathanMagnan]

Hello @BEagle1984 ,

Thank you for reporting, we will look at this.

Best Regards,

Jon

[JonathanMagnan]

Hello @BEagle1984 ,

The issue happens because our library cannot discover that your table has an AUTOINCREMENT column.

You can make it works by specifying it in your table definition:

[CustomerID] [INTEGER] PRIMARY KEY AUTOINCREMENT,

It currently works with the System.Data.SQLite as we have a custom logic when no identity has been found.

We will look to add a similar logic for Microsoft.Data.Sqlite but meanwhile, you have an alternative solution.

Best Regards,

Jon

[JonathanMagnan]

Hello @BEagle1984 ,

The v3.0.34 has been released.

In this version, we added the same fix when no identity is found that the System.Data.SQLite. A column with an INTEGER type acts like an identity when this is the only PK column. We added this missing rule to the Microsoft.Data.Sqlite provider.

Best Regards,

Jon

[BEagle1984]

Thank you @JonathanMagnan for the quick reply. The workaround works like a charm and we are bulk inserting like crazy. 💪

[JonathanMagnan]

Great to hear!

Don't hesitate to contact us if needed!

Best regards,

Jon