ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #grails
Our Grails application uses the database-migration plugin (Liquibase-based) with changelogs under grails-app/migrations, and we are standardizing how schema changes ship to production. The goal is a rollback story that actually works when a release must be reverted, not just one that exists on paper. The uncertainty is around destructive changeSets. Liquibas
Goal Determine the best second‑level cache strategy to minimize stale reads when domain objects are updated concurrently. Constraints Grails maps domain classes to Hibernate entities. The cache configuration is declared in the domain class’s static mapping block, e.g. cache usage: 'read-write' or cache usage: 'nonstrict-read-write' . The choice affects soft‑
In a Grails application that uses the database-migration plugin, schema evolution is tracked through ordered Liquibase changesets. The plugin supports explicit rollback blocks, but rollback safety depends on whether the underlying database treats DDL as transactional. Many storage engines auto-commit DDL, so a failed rollback can leave the schema in an inter
Goal Determine a consistent date‑binding strategy for a Grails application that serves users across multiple regions while preserving the intent of user‑entered dates and avoiding unexpected shifts after persistence. Constraints and uncertainties The grails.databinding.dateTimeZone property (introduced in Grails 5.3) controls how incoming date strings are pa
When a Grails service injects the default RestTemplate to invoke an external HTTPS endpoint that presents a self‑signed certificate, the request fails with an SSL handshake error indicating the certificate chain cannot be validated. The goal is to configure the client to trust that certificate for outbound calls while avoiding unintended side effects on othe
Grails 4 and later default to HikariCP for GORM data sources, so low-traffic cost tuning is configured through dataSource.properties.* keys in application.yml rather than legacy Tomcat pool settings. The goal is to reduce database connection or session costs for a workload that sits idle for extended periods. HikariCP interprets minimumIdle as a floor and ma
In current Grails releases, the list method maps max and offset to Hibernate's setMaxResults and setFirstResults, producing SQL LIMIT/OFFSET clauses. However, the interaction between GORM's convenience binding and Hibernate's execution model raises unresolved questions for deep pagination. As offset values grow, the database must scan and discard skipped row
liquibase
hibernate