CODEWITHSUNDEEP
databasegrailsgrails-ormliquibase
Clark Wright
Clark Wright

Reputation: 751

Using liquibase, how to handle an object model that is a subset of database table

Some days I love my dba's, and then there is today...

In a Grails app, we use the database-migration plugin (based on Liquibase) to handle migrations etc.

All works lovely.

I have been informed that there is a set of db administrative meta data that we must support on every table. This information has zero use to the app.

Now, I can easily update my models to accommodate this. But that answer is ugly.

The problem is now at each migration, Liquibase/database-migration plugin, complains about the schema and the model being out of sync.

Is there anyway to tell Liquibase (or GORM) that columns x,y,z are to be ignored?

What I am trying to avoid is changesets like this:

changeSet(author: "cwright (generated)", id: "1333733941347-5") { dropColumn(columnName: "BUILD_MONTH", tableName: "ASSIGNMENT") }

Which tries to bring the schema back in line with the model. Being able to annotate those columns as not applying to the model would be a good thing.

Upvotes: 0

Views: 410

Answers (1)

Visionary Software Solutions
Visionary Software Solutions

Reputation: 3848

Sadly, you're probably better off defining your own mapping block and taking control of the Data Mapper (what Hibernate essentially is) yourself at this point. If you need to take control of the way the database-integration plugin handles migrations, you might wanna look at the source or raise an issue on the JIRA. Naively, mapping your columns explicitly in the domain model should allow you to bypass unnecessary columns from the DB.

Upvotes: 0

Related Questions