Repository navigation
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: ae01fae1-3e57-4d55-ad2c-f746a2d1084d
roji
force-pushed
the
roji-pgvector-ef-11-convention
branch
from
October 23, 2026 10:05
fb05a0e to
4616510
Compare
Contributor
Author
ankane
added a commit
that referenced
this pull request
Oct 24, 2026
… SparseVector properties - #64 Co-authored-by: Shay Rojansky <roji@roji.org> Assisted-by: Copilot App
Member
|
Thanks @roji! Merged in the two commits above (one to support |
Member
|
Also, fwiw, EF Core doesn't set the properties even when the query returns them (which doesn't seem great). var items = await ctx.Items.FromSql($"SELECT * FROM efcore_items ORDER BY embedding <-> {embedding} LIMIT 5").ToListAsync();
Assert.Null(items[0].Embedding); |
Contributor
Author
|
Thanks! Yeah, that seems like a bug on the EF Side - opened dotnet/efcore#39398. |
Member
|
Awesome, thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@ankane, following your preference in #63, this prepares Pgvector.EntityFrameworkCore 0.4.0-rc.1 for .NET 11 and EF Core 11, including the convention to stop auto-loading vector columns. This is a release candidate because EF Core 11 has not yet been released.
Closes #59
Summary
0.4.0-rc.1, targetingnet11.0only, with Npgsql.EntityFrameworkCore.PostgreSQL11.0.0-rc.1.1.IConventionSetPluginusing EF 11'sAutoLoadConventionto excludeVector,HalfVector, andSparseVectorproperties from automatic entity loading by default. Explicit model configuration takes precedence;BitArraybehavior is unchanged.build/net11.0, update the SDK/CI configuration, and document explicit projections and model-level opt-in viaMetadata.IsAutoLoaded = true.Rebased directly onto the latest upstream
master. This PR no longer depends on #63 and does not include the proposed EF 10 release. For EF Core 9 and 10, the README continues to recommend version0.3.0.Lower-level Pgvector and Pgvector.Dapper versions, target frameworks, and dependency policies are unchanged. Per-query auto-loading opt-in is out of scope.
Validation
Pgvector.EntityFrameworkCore.0.4.0-rc.1.nupkgsuccessfully; verified version0.4.0-rc.1, the EFCore.PG 11 dependency, and onlylib/net11.0andbuild/net11.0assets.No packages were published.