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
We found ourselves behind on quill versions and are working on upgrading. Before making the jump to 4.x, we pinned ourselves to (at the time) the highest 3.x. As this version as been adopted we found this bug. We are testing to see if it persists on 4.x and will update this issue when we find more.
We found that flat join code that produced valid SQL in 3.5.1, produced invalid SQL in 3.16.5. Depending on the schemas being joined this could produce syntactically correct but logically invalid SQL, leading to subtly wrong behavior.
Expected behavior
Quotes compile to the same SQL across versions.
Actual behavior
Quotes don't compile to the same SQL across versions.
Version: (e.g.
3.16.5
)Module: (e.g.
quill-jdbc
)Database: (e.g.
postgres
)We found ourselves behind on quill versions and are working on upgrading. Before making the jump to 4.x, we pinned ourselves to (at the time) the highest 3.x. As this version as been adopted we found this bug. We are testing to see if it persists on 4.x and will update this issue when we find more.
We found that flat join code that produced valid SQL in 3.5.1, produced invalid SQL in 3.16.5. Depending on the schemas being joined this could produce syntactically correct but logically invalid SQL, leading to subtly wrong behavior.
Expected behavior
Quotes compile to the same SQL across versions.
Actual behavior
Quotes don't compile to the same SQL across versions.
Steps to reproduce the behavior
Given this example query:
Quill 3.5.1 produced this valid SQL:
But Quill 3.16.5 produces this SQL (note the aliases used in the
WHERE
andSELECT
clauses):Workaround
Modifying my flat-join code to this produces the logically correct SQL that matches the behavior, although not exactly the syntax, of the 3.5.1 SQL:
@getquill/maintainers
The text was updated successfully, but these errors were encountered: