In the latest versions, changing your classes *should* magically
update your tables. This is because the hibernate3 plugin now "drops"
the tables before trying to create them. Make sure your configuration
matches the following:
<componentProperties>
<drop>true</drop>
<jdk5>true</jdk5>
<propertyfile>target/classes/jdbc.properties</propertyfile>
<skip>${maven.test.skip}</skip>
</componentProperties>
Matt
On 3/29/07, Dale Newfield <[EMAIL PROTECTED]> wrote:
VJ22 wrote:
> it works after I dropped the schema and re-created it......
>
> Any clue why this is like this ?
Changing your classes doesn't magically change the DB. (I think
somewhere there is a setting (hibernate.hbm2ddl.auto) that tells
Hibernate to update the DB if it starts and finds the DB doesn't match,
but I've never tested it.) Not sure what version of appfuse you're
using, but if 1.9.x I think there's a "db-update" ant target that might
help. I usually just drop and recreate, though. (I think JPA might
imply you're using 2.0, so ignore the ant suggestion.)
-Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://raibledesigns.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
