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

Expose PostgreSQL JSON operators #4

Closed
roji opened this issue Apr 14, 2016 · 4 comments
Closed

Expose PostgreSQL JSON operators #4

roji opened this issue Apr 14, 2016 · 4 comments

Comments

@roji
Copy link
Member

roji commented Apr 14, 2016

From @roji on September 8, 2015 7:56

PostgreSQL supports a wide array of JSON operations. We may be able to translate at least some JSON operations in LINQ queries to PostgreSQL for backend processing - this would prevent the entire resultset from being pulled in to the client.

Explore the Newtonsoft.JSON API to see what can be done. We also probably don't want to take a dependency on Newtonsoft.JSON from the EF7 provider, so reference the JSON methods via reflection.

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#771

@ma3yta
Copy link

ma3yta commented Sep 28, 2016

Hello @roji,

how progress on this task?

@roji
Copy link
Member Author

roji commented Sep 28, 2016

Unfortunately not, I've been busy with more important/basic things...

I'm also not 100% sure it's a good idea to attack this before the general EFCore JSON story becomes clearer: dotnet/efcore#4021 (comment). We would risk going down our own specific path etc.

@roji
Copy link
Member Author

roji commented Feb 6, 2018

It may be a good idea to look at standardized SQL/JSON support: https://wiki.postgresql.org/wiki/Postgres_Professional_roadmap#SQL.2FJSON_standard. This may even be a cross-database thing.

@roji roji mentioned this issue Mar 10, 2018
@roji
Copy link
Member Author

roji commented May 11, 2018

Superceded by #334

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

2 participants