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.

Sign up for GitHub

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

Jump to bottom

Expose PostgreSQL XML functions #7

Open
roji opened this issue Apr 14, 2016 · 5 comments
Open

Expose PostgreSQL XML functions #7

roji opened this issue Apr 14, 2016 · 5 comments
Labels
enhancement New feature or request good first issue Good for newcomers
Milestone
Backlog

Comments

@roji
Copy link
Member

roji commented Apr 14, 2016

From @roji on September 8, 2015 8:4

PostgreSQL supports xpath matching, which we can expose to the user when corresponding methods are used in the LINQ query. This would prevent the entire resultset from being pulled in to the client.

It may be a good idea to provide an opt-out for this in case there's trouble or client-side evaluation is preferred. At the query and model levels.

Copied from original issue: npgsql/npgsql#773
@roji roji added ef core enhancement New feature or request good first issue Good for newcomers labels Apr 14, 2016
@roji roji mentioned this issue Apr 14, 2016
Closed
@roji roji removed the ef core label Apr 19, 2016
austindrenski referenced this issue in austindrenski/npgsql-efcore.pg May 14, 2018
@austindrenski
Changes new attribute visibility and provides hooks for registering n…
35f7d00 
…ew range operator methods for translation (e.g. client code can define and register a method that supports client evaluation). The goal is to build on CustomBinaryExpression and make it easier to add new operators (e.g. XML operators from issue #7). With the current structure, additional operator classes can be codified in 3 files: Npgsql{type_name}OperatorType, Npgsql{type_name}OperatorAttribute, and Npgsql{type_name}OperatorTranslator.
@roji roji added this to the Backlog milestone Jun 9, 2018
@austindrenski
Copy link
Contributor

This has been around for a while. I'm going to take a run at for 2.2.0.

@austindrenski austindrenski self-assigned this Jun 24, 2018
@austindrenski austindrenski removed the good first issue Good for newcomers label Jun 24, 2018
@austindrenski austindrenski modified the milestones: Backlog, 2.2.0 Jun 24, 2018
@roji
Copy link
Member Author

roji commented Jun 24, 2018

It's been around for a while, but it hasn't ever been requested by an actual user :) I suspect that with xml going out of fashion hardly anyone needs this...

I'd suggest concentrating our efforts elsewhere until this gets some votes etc...

@austindrenski
Copy link
Contributor

Possibly relevant:

dotnet/efcore#12795 (comment)

@roji roji modified the milestones: 2.2.0, 3.0.0 Nov 15, 2018
@austindrenski austindrenski removed their assignment Nov 15, 2018
@austindrenski austindrenski added the good first issue Good for newcomers label Nov 15, 2018
@roji roji modified the milestones: 3.0.0, Backlog Aug 24, 2019
@ahmednfwela
Copy link

@roji Is there a way to access postgres XML functionality before this is implemented ?

@roji
Copy link
Member Author

roji commented Oct 14, 2024

Yes, use SQL queryinghttps://learn.microsoft.com/en-us/ef/core/querying/sql-queries?tabs=sqlserver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@roji @austindrenski @ahmednfwela