Using Roo with an existing database
I have an existing database that I have to write a simple web based CRUD application for. I'm considering using Roo. The problem I've seen so far is that Roo wants to create it's own database based on the domain objects. Is there or is there going to be a reverse mapping? Something like this exists in Django:
I think it's very useful because in most corporations the data already exists in some relational form and it's the applications that change or get replaced.
Configuring Roo with an existing DB
The problem I currently have is that in my existing database I don't have the version (required by Roo) on my tables. Is it something that can be solved only by adding the version column to every table in the existing schema?
Also, when I map a Roo entity to an existing table with an already existing primary key (--identifierColumn / --identifierField) there is no option for defining a finder on that column.
Is there a way to enforce foreign key relationships with Roo?