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
If you do findVersions() on a history object that references a non-versioned and then a versioned object again, a systime <@ null will be added to the query (postgres) which will of course always fail.
This will erronously add a systime constraint which never matches (systime <@ null) in postgres. H2 adds a syntactically different, but it has the same problem. Other databases are untested but assumed to fail the same way.
If you do
findVersions()
on a history object that references a non-versioned and then a versioned object again, asystime <@ null
will be added to the query (postgres) which will of course always fail.ie.
This will erronously add a systime constraint which never matches (
systime <@ null
) in postgres. H2 adds a syntactically different, but it has the same problem. Other databases are untested but assumed to fail the same way.Expected behavior
Return list of matching results
Actual behavior
Always returns zero records
Steps to reproduce
#3082 has a testcase showing it
The text was updated successfully, but these errors were encountered: