-
-
Notifications
You must be signed in to change notification settings - Fork 68
allow to customize json search function #188
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
base: master
Are you sure you want to change the base?
Conversation
/** | ||
* Postgresql {@code jsonb_path_exists} function to use | ||
*/ | ||
public static String JSONB_PATH_EXISTS = "jsonb_path_exists"; | ||
|
||
/** | ||
* Postgresql {@code jsonb_path_exists_tz} function to use | ||
*/ | ||
public static String JSONB_PATH_EXISTS_TZ = "jsonb_path_exists_tz"; | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi. This code essentially introduces global mutable variables which is well known anti-pattern.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well, whole jsonb support is based on static methods so i didnt seen any other way to make fields accessible. i used same "pattern" as for enabling date time support.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sure there are other ways to achieve this. Yeah, configuring date time support in this way was a quite a mistake I must say.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i moved configuration to QuerySupport
Resolves #187