ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Grails 6 teams choosing between Where queries, Criteria API, and dynamic finders: Where queries win for new code with compile-time safety and composability, Criteria stays for advanced projections, dynamic finders only for trivial lookups.
Keep HTTP input out of GORM writes by validating command objects before service transactions, and verify rollback behavior in your Grails version.
Grails services are transactional by default, but @Transactional can be too coarse. GORM's withTransaction gives you programmatic control for conditional commits, nested logic, and retry scenarios—if you understand its rollback rules and nesting quirks.
Learn how Grails GORM dynamic finders let you replace boilerplate HQL with concise, readable service methods while understanding their limits and refactoring risks.
This note outlines how to structure a Grails service layer using declarative transaction management, covering requirements, minimal design, trust boundaries, verification steps, failure modes, and when to adopt a more complex architecture.
Stop repeating the same GORM filters. Learn how DetachedCriteria lets you define query logic once, combine it safely, and execute it inside an active Grails session.
Learn how to use Grails GORM’s type‑safe ‘where’ query DSL to build paginated, sorted, and projected queries. A concrete example with a Person domain shows how to avoid HQL pitfalls and keep your code refactor‑safe.
Dynamic finders let you query Grails domain classes with a concise method name. This article explains how they work, shows a working example, and lists limits and common pitfalls so you can use them safely and efficiently.
Grails GORM’s schema‑per‑tenant strategy lets you isolate tenant data automatically. This blog walks through configuration, a tenant resolver, domain classes, a concrete example, and trade‑offs to help you decide if it fits your SaaS project.
groovy
grails
hibernate