> I shudder every
> time I need to make a database change and then import the new updated
> model and then make all my relationship changes again and regenerate all
> affected java again (but maybe I'm just not good at using the tools yet -
> certainly I wish my customer would have let me take the time to design the
> entire db up front - but he's much more into rapid prototype mode where we
> get incremental results quickly).
Just a comment
I find EOModeler combined with the code merging tool to work just fine.
Although my database is done, my model is not complete. I'm taking it a
little at a time and making each piece work. If I don't have a table in the
model, I just update the model. If I need to add a relationship, I just add
it, Generate Java Code, and merge. The merge utility is really awesome. I
haven't had any problems and haven't lost any custom code.
--Marc Respass
