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
Starting from release 0.37.2 it seems that the filtering operation performed by a WHERE statement has no effect when applied on a table obtained after performing multiple (INNER) JOIN operations.
The reason why I suspect that this has something to do with Dolt is simply that I cannot reproduce this error using an SQLite backend.
I have extracted an MWE from a recording application, where we are tracking product locations in a sequence of images (frames).
The MWE database can easily be created by applying the following command in a fresh dolt repo: $ dolt sql <doltdump.sql
Hi @Jannick-v, thanks for filing this and using Dolt. We'd love to hear about your use case. You can email me (brianf@dolthub.com) or swing by our Discord if you'd like to share.
Hi all,
Thanks for the quick fix included in the latest release!
This fully resolves the issue I was facing last week, hence I am closing this issue.
Great work!
Starting from release
0.37.2
it seems that the filtering operation performed by aWHERE
statement has no effect when applied on a table obtained after performing multiple (INNER
)JOIN
operations.The reason why I suspect that this has something to do with Dolt is simply that I cannot reproduce this error using an SQLite backend.
I have extracted an MWE from a recording application, where we are tracking product locations in a sequence of images (
frames
).The MWE database can easily be created by applying the following command in a fresh dolt repo:
$ dolt sql <doltdump.sql
Once created, run the following query:
The result of this query in
dolt 0.37.2
and higher is unexpected:dolt 0.37.6
resultsdolt 0.37.2
results:The result in older versions of dolt (here
0.37.1
) is identical to the result obtained with anSQLite
backend:How do I fix this issue?
The text was updated successfully, but these errors were encountered: