Generate CRUD Operations

Hi Everyone,
I have a physical data model in Rose Data Modeler and ERwin. I would like to generate CRUD operations in Java but do not see an option for this in either Rose or ERwin.

Is there a thrid party package that could do this using the Rose or ERwin file? I need to keep the model in either of those but would like to generate CRUD operations instead of hand coding them. Using stored procedures is an option but I would have to check with others on this as in the past CRUD's have always just been coded in Java using JDBC.

I am using DB2 v9.1 but want standard SQL for the CRUD operations.

Thanks for the advice.

I know of a number of CRUD generators, but none that will work directly with your model's files....

I would like to suggest that you (attempt to) persuade people to go the SP route. One primary reason:

1) You decrease the "attack surface".

If you expose raw tables to the application (even for read) then there are attacks which are possible that are easily prevented by only exposing controlled stored procedures...

But wait...

2) You isolate the physical model from the logical model.

A few years ago I was working of a LARGE database. One table had 37 fields (it was fifth form normal), of which 6 of them were read frequently, 2 of them were updated frequently, and the remainder had use-cases that were less common.

When a recognized leader in DB tuning was brought in, they re-organized this into three distinct tables (denormalizing the data) and ssigned the tables do different drives (speed/capacity) on the SAN. Base performance increased by over 35%, and the "degradation point" was moved up to nearly 5x the numberof transactions per minute. All of this was done without a single change the the application BECAUSE of the SP approach.

...There's More...

3) Programmers [Java, C++, VB, C#, etc] THINK differently than DBA's.

And this is a good thing. The programmers typically think in terms of iterating through data, while DBA's (properly) think in terms of set theory.

THe SP approach facilitates this. My experience has been that many programmers when presented with a truely optimized database schema, will tend to question [or even declare as outright wrong] an architecture which is in fact proper.

Sorry no Ginsu Knives :D:D:D