EntityFrameworkCore.Jet
EntityFrameworkCore.Jet copied to clipboard
bubibubi
Entity Framework Core provider for Access database
Probably EF Core enforce 1-1 relationships using unique indexes so Design Tests should not work anymore
In DB First scenario, the generated ModelContex.cs (from Scaffold-DbContext command) doesn't compile, issuing the following error: Error CS1061: 'DbContextOptionsBuilder' does not contain a definition for 'UseJet' and no accessible extension...
If you specify AsNoTracking on a query, it throws an error - System.InvalidOperationException: 'variable 'materializationContext' of type 'Microsoft.EntityFrameworkCore.Storage.MaterializationContext' referenced from scope '', but it is not defined' Example: var list...
https://github.com/bubibubi/JetEntityFrameworkProvider/issues/28
The Lazy-Loading or Loading of the navigation properties in general is not working properly. I used your tutorial from your wiki-page to create the model and the database. All worked...
Providers are usually compatible with future .NET versions, not just the version that was current at the time of the release. (They are usually only compatible with one specific EF...
For example, the store type `varbinary(max)` should not be supported. The Jet equivalent would just be a `longbinary`.
With the release of .Net RC 1 and EF Core 8 it is time to start work on a compatible version of EFCore.Jet Alpha 1 is now out and available...
I've just started a simple project to test if i can read an access db with EF and the Jet Provider. But the scaffolding leads to a COM Exception 0x800A0CB3....
