cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tobias SCHOESSLER <>
Subject best practice for handling database schema changes
Date Thu, 30 Nov 2006 14:59:50 GMT

<br><font size=2 face="sans-serif">hi,</font>
<br><font size=2 face="sans-serif">What is the best practice for handling
changes to the database schema once a cayenne mapping was created? </font>
<br><font size=2 face="sans-serif">We use the 'reverse engineer from database'
feature to create an initial mapping. But then we usually have to do manual
changes like map some pks, add flattened relationships, etc.</font>
<br><font size=2 face="sans-serif">If then the database schema needs to
be changed we usually have a problem as 'reverse engineer from database'
overwrites everything. There seems to be the possibility to replace only
selected tables but if you do this the relationships are messed up. Is
there a way to &nbsp;merge the changes with the current model/mapping?</font>
<br><font size=2 face="sans-serif">thanks</font>
<br><font size=2 face="sans-serif">Tobias</font>

View raw message