You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/** * Path exists - for the given path in a JSON document. */ExpressionList<T> jsonExists(StringpropertyName, Stringpath);
/** * Path does not exist - for the given path in a JSON document. */ExpressionList<T> jsonNotExists(StringpropertyName, Stringpath);
/** * Equal to expression for the value at the given path in the JSON document. */ExpressionList<T> jsonEqualTo(StringpropertyName, Stringpath, Objectvalue);
/** * Not Equal to - for the given path in a JSON document. */ExpressionList<T> jsonNotEqualTo(StringpropertyName, Stringpath, Objectval);
/** * Greater than - for the given path in a JSON document. */ExpressionList<T> jsonGreaterThan(StringpropertyName, Stringpath, Objectval);
/** * Greater than or equal to - for the given path in a JSON document. */ExpressionList<T> jsonGreaterOrEqual(StringpropertyName, Stringpath, Objectval);
/** * Less than - for the given path in a JSON document. */ExpressionList<T> jsonLessThan(StringpropertyName, Stringpath, Objectval);
/** * Less than or equal to - for the given path in a JSON document. */ExpressionList<T> jsonLessOrEqualTo(StringpropertyName, Stringpath, Objectval);
So Postgres and Oracle have JSON expressions and currently with Ebean you need to use a raw() expression to have these in your where clause like:
This enhancement would add 'path exists' and 'value at path equals ?' expressions to the ExpressionList to make this much nicer to use.
The text was updated successfully, but these errors were encountered: