Closed ryanmitchell closed 1 year ago
I assume you're talking about queries you're writing rather than ones this driver is making?
if so, what about making it a storedAs
column in your own migration - that allows you to query it independently but it's still using the JSON field field so the driver's code doesn't need to change.
It's also when using entries
fieldtype for relationships with the blueprint
filter.
Another issue is trying to query entries for a specific site with a certain blueprint - right now you're forced to fetch the original, loop through them to get the localized entry, and filter whether they're published or not, which is rather cumbersome.
The localised entries issue should be solved by the data propagation PR which is open at the moment.
Originally posted by @FrittenKeeZ in https://github.com/statamic/eloquent-driver/issues/114#issuecomment-1420531869