ppazos commented on issue #14594: URL: https://github.com/apache/grails-core/issues/14594#issuecomment-2907907526
I know this has been a desired feature for a long time, though today it might be a deal breaker not to have support to JSON columns, since it's a common practice for today's complex requirements to have some kind of denormalization and document orientation inside a relational DB. Though I don't know what's the workload required for the GORM to have this on its DSL and of course in the query APIs (dynamic filters and criteria builders), and also on the constraints. We also need to consider today's core team is 100% community based and there are not many contributors. I would like to know if this isn't planned yet so I can look for alternatives, like @danieljoeblack shared, there is a workaround at the HQL level, though JSON_EXTRACT seems to be a MySQL function and might not work on other databases. The other option is to actually have two databases, one relational and one JSON (Couch, Mongo, etc), and it seems that Grails can connect to different data sources and tell domain classes to use one or the other (https://stackoverflow.com/a/14894944/1644320), so this affect domain model design, but it's doable. I think the second option might be the more reliable way right now, though it adds a new architectural component that needs to be managed, has extra costs, etc. Not ideal, specially for SQL guys :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
