fix(db): Fix JSON handling in WHERE statements for postgres#56504
fix(db): Fix JSON handling in WHERE statements for postgres#56504nickvergessen merged 5 commits intomasterfrom
Conversation
|
https://dev.mysql.com/doc/refman/8.4/en/json.html
|
5ba0766 to
fd912da
Compare
fd912da to
7e0e1e2
Compare
|
@nickvergessen Thank you for fixing this.
Is it still not matching or did you fix that as well? |
I fixed it with a provider based switch in the query location |
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
…ecting Signed-off-by: Joas Schilling <coding@schilljs.com>
7e0e1e2 to
7c870a8
Compare
|
Nice, its actually only mysql but not mariadb, so using strict mode in the comparison |
|
Oracle 11 is failing: |
Signed-off-by: Joas Schilling <coding@schilljs.com>
Fix #56497
cc @julien-nc the WHERE is now at least not throwing an exception anymore, but it is NOT matching in MySQL at least. I added a unit test so you can see the result
Checklist
3. to review, feature component)stable32)