-
Notifications
You must be signed in to change notification settings - Fork 234
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
Add support for PGroonga.EntityFrameworkCore EF.Functions #1053
Conversation
@kinosang you're right that evaluatable filter is still needed in 3.0 - I've reopened dotnet/efcore#13454 to discuss. However, just to be sure, this should only be needed if we have function calls which don't reference any columns, and which should still be evaluated at the server. Good examples are DateTime.Now, random number/guid generation and the like. Can you confirm you have cases like this with PGroonga (and out of curiosity, which one(s))? |
@roji PGroonga has two types of functions, they are: 1.functions without parameter such as All the functions should be translated and evaluated at the server. |
These are global checks on the database, right? i.e. whether the database is writable, or to make pgroonga do something at the global level? |
Merged and backported for 3.0.1. |
Yes, the But no, the The |
Thanks for the added details @kinosang! I need to put together a page with links to interesting/relevant external plugins, where yours could be listed (npgsql/doc#13). |
I'll also try to publish 2.2.6 soon so that the PGroonga support there is unblocked as well. |
Unfortunately, it seems a filter is still required to run DbFunctions on ef core 3.0.