MappedSuperclass Alternatives in Grails

Question

In many past projects, I used this JPA / Hibernate approach to add auditing capabilities to a system. It's very effective and unobtrusive.

Is there a Grails @MappedSuperclass alternative (short of coding domain model objects in Java instead of Groovy)? How can one declare a parent class in a table-per-subclass approach without having a table created for it? I've read the GORM documentation (5.2.3 Inheritance in GORM) but besides the table-per-hierarchy vs. table-per-subclass discussion, I did not find any details on how to do this.

Alternatively, what is the recommended way to achieve this type of auditing in Grails?

Yes for some reason this does work in Grails 2 anymore the Abstract class gets there own table definition? Have asked on the Grails forum but nobody seems to know why this has been changed. Anybody know why or know a workaround or setting? — , Mar 04 '12 at 10:22

score 6 · Accepted Answer · edited Sep 27 '21 at 07:17

Essentially, it's as simple as declaring the MappedSuperclass as abstract and Grails will not create a table for it. I realized by re-reading the manual:

GORM supports inheritance both from abstract base classes and concrete persistent GORM entities. I.e. concrete classes are persistent, so abstract ones are not. Pays to read more carefully.

E.g.

abstract class Auditable {
    Date dateCreated
    Date lastUpdated
}

class Book extends Auditable {
    String title
    String description
}

Only the book table will be created and it will have the date_created and last_updated columns. Furthermore, as an added bonus, the dateCreated and lastUpdated properties are auto time-stamped by Grails.

@HussainFakhruddin you mean 2.x right? We are using 2.5.4 – svaret Apr 05 '17 at 08:58 — svaret, Apr 05 '17 at 08:58

MappedSuperclass Alternatives in Grails

1 Answers1

Linked