This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes Groovy and the fly likes Grails - Exisiting Oracle Table Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Languages » Groovy
Bookmark "Grails - Exisiting Oracle Table" Watch "Grails - Exisiting Oracle Table" New topic
Author

Grails - Exisiting Oracle Table

Bill Lee
Greenhorn

Joined: Feb 02, 2007
Posts: 20
Grails is very straightforward in creating NEW tables, but I am having trouble mapping to an EXISTING table. One of the problems being that it appends id and version to each table. Maybe I need to add some entries for static mapping??? Thanks.
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5852
    
    7

You can declare a custom identify for your tables, see the docs at Custom%20Database%20Identity
Then Grails will not attempt to create an id field.

Also you can turn off optimistic locking, which prevents the version field form being created: http://grails.org/doc/1.1.x/ref/Database%20Mapping/version.html

These questions made me ask if you have read the Grails docs, and/or if you have purchased a Grails book - there are several good ones on the market.


JBoss In Action
 
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
 
subject: Grails - Exisiting Oracle Table
 
It's not a secret anymore!