Skip to content
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

findVersions across a historyless and a historied object finds nothing #3083

Open
tobias- opened this issue May 31, 2023 · 0 comments
Open

Comments

@tobias-
Copy link
Contributor

tobias- commented May 31, 2023

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.

ie.

QHistoriedA(db)
  .where()
  .historyLessB.historiedC.deleted.isNotNull
  .findVersions()

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant