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

EF Core 9 support #252

Open
ChrisJollyAU opened this issue Aug 17, 2024 · 1 comment
Open

EF Core 9 support #252

ChrisJollyAU opened this issue Aug 17, 2024 · 1 comment
Milestone

Comments

@ChrisJollyAU
Copy link
Member

Opening this issue for any questions on the EF Core 9 support.

Work has begun and the master branch is now targeting EF Core 9 (dependent on preview 7).

EF Core 9 does work on .Net 8 so you can update the EF Core part without changing the .Net version.

Currently it is only available on the daily build feed with myget, with hopefully an alpha 1 on nuget before the end of the month

@ChrisJollyAU ChrisJollyAU added this to the 9.0.0 milestone Aug 17, 2024
@ChrisJollyAU ChrisJollyAU pinned this issue Aug 17, 2024
@ChrisJollyAU
Copy link
Member Author

EFCore.Jet Alpha 1

Welcome to the first release of EFCore.Jet 9. This is targeting EF Core 9 preview 7 and will run on .Net 8+.

New Features

Bug fixes

  • Tests: Multiple fixes due to optimization improvements made by EF Core itself
  • Fix shared column validating when using view splitting Fix View splitting #258
  • Improvements to the migrations sql Improvements to migrations #256
    • Updating a column has the following improvements
      • Don't generate an unnecessary ALTER TABLE
      • If the column is being made non-nullable (when originally null), create an UPDATE statement to set the value of that column to the default value for those where the current value is NULL
  • Null Semantics Tests: A test used the parent BoolTypeMapping and true was translated as 1. Jet uses -1 for true so override default behaviour to produce the sql literal of TRUE. Also adds some further tests to the overrides so we can test the sql Improve Null Semantics tests #260
  • Use the lowest possible value of DateTime (1 Jan 100) when using a FirstOrDefault. A 0 in Jet/OLE Automation is not actually the lowest possible value
  • The type mapping for the translation of TimeOfDay was returning a DateTime and not TimeSpan
  • When reading a value for the TimeSpan and TimeOnly don't convert the default 0 to the c# 0 like we do for DateTime
  • A primary key with type of short can also be mapped to a counter type if it needs to be an auto incrementing key

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

No branches or pull requests

1 participant