Hi, Bobby
This has been discussed with the persistence team. We were advised
to set the dropandcreatetables deployment param to false during the
upgrade so tables will not be dropped and re-created. If you see things
behave differently in your test, please file an issue.
Thanks,
- Hong
On 10/25/2010 12:57 PM, Bobby Bissett wrote:
> This is mostly a question for Hong, but others may have an opinion since this touches on JPA as well.
>
> I have an app deployed in GF v2.1.1 with this in its persistence.xml file:
> <property name="toplink.ddl-generation" value="drop-and-create-tables"/>
>
> So, obviously, every time I redeploy the app the tables get cleared out, ready to test again. My question: after I upgrade this domain to 3.1, should I expect the tables to be dropped/created? I thought that the applications were redeployed, and so this would be triggered in the JPA provider, but that's not what I'm seeing.
>
> I wanted to check so I can adjust a test accordingly and/or file an issue.
>
> Thanks,
> Bobby
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>