-
Notifications
You must be signed in to change notification settings - Fork 10
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
CasesManagement add PostgreSQL support #373
Comments
For the core INDICE extensions it is doable to introduce support for PostgreSQL. This actually is related to src/Indice.EntityFrameworkCore/Functions/ModelBuilderExtensions.cs We can discuss to see what we need to do to support it and there are already tests in-place for these in test/Indice.Services.Tests/FilterClauseQueryableExtensionTests.cs so we can replicate the same behavior for PostgreSQL cc @dkarkanas |
A good candidate for JSON_VALUE equivalent in PostgreSQL could be |
After some investigation, So an expected working query would look like this: SELECT d."Id", d."Data", d."Extras", d."Metadata", d."Name"
FROM "Dummies" AS d
WHERE jsonb_path_query_first(d."Data", '$.displayName')::text ILIKE '%κων%'
AND (jsonb_path_query_first(d."Data", '$.period.to')::text)::timestamptz > '2024-01-17T00:00:00.0000000'
AND jsonb_path_query_first(d."Metadata", '$.NAME')::text = '"Thanos"' |
After testing the following have been found and need to be fixed/researched so that the cases management system can run using PostgreSQL engine.
json
columns uses MsSql fucntions by default. This needs to be configurable.AddWorkflow
extension method allows for a delegate to configure the Elsa efcore dbcontext giving the ability to use other engines for Elsa as well.Other checks that need to be made
The text was updated successfully, but these errors were encountered: