GORM JSONArrayQuery.Contains isn't compatible

[ns-kliu]

GORM JSONArrayQuery.Contains isn't compatible

[fulghum]

Good find @ns-kliu. I tracked this down to the JSON_ARRAY function not properly handling arguments when they come in as bind vars, and I opened #1919 with the fix. Thank you for pointing out this problem and sorry about the initial delay in us investigating! 🙏

[ns-kliu]

Can any maintainer have a look?

[timsehn]

@fulghum will look today.

--Tim

[fulghum]

Hey @ns-kliu, thanks for taking the time to report this and to provide such a nice repro case! I've got the repro going and am seeing the same behavior you describe. The first thing I've noticed is that the first two queries (which don't return the user that was just created) are both using prepared statements, and the third query (which works correctly) is simply being executed without being prepared and then having bind vars plugged in. Based on that, it seems like there's something going on with query preparation. I've tried disabling prepared statements to confirm that guess, but the configuration I provided doesn't seem to actually disable them.

I'll keep digging in and see what else I can find in the debugger.

[fulghum]

I kept digging deeper into this one and noticed that the client/GORM is sending over the type CHAR for the bind var, but Vitess is swallowing that info from the client and instead labeling it as VARBINARY when it sends it to go-mysql-server for processing. I just merged in a fix to our fork of Vitess to stop overwriting CHAR with VARBINARY for bind vars, and I confirmed that change enables JSON_ARRAY to handle the prepared query correctly now.

I've got a few more steps to get that change available in go-mysql-server and dolt and will close this issue once those are done.