Thanks for the response!
Mitesh Meswani wrote:
>
> sandeepspatil wrote:
>> Hello folks,
>>
>> We are developing a commercial desktop application for which we have
>> decided
>> to use JPA as the ORM mapping tool. This is the first time I'm using an
>> ORM
>> tool.
>>
>> I understand that it is all OK when we are starting the application from
>> scratch. But after the first release, if we are required to change a
>> table's
>> schema, by say adding or deleting a table column, how do we handle that
>> through JPA?
>>
> The DDL generation feature of JPA provider is helpful at development
> time. You can start with a version of DDL script generated initially and
> then stop using DDL generation feature. You can manually update the
> initial script to adopt to your changes.
>
> Regards,
> Mitesh
>> I came across one such topic here:
>> http://weblogs.java.net/blog/fabriziogiudici/archive/2008/05/simple_database.html
>>
>> But he doesn't give the implementation there.
>>
>> Can someone please throw some light?
>>
>> Thanks much,
>> Sandeep
>>
>
>
--
View this message in context: http://www.nabble.com/How-to-handle-table-schema-updates-in-JPA-tp18320972p18340459.html
Sent from the java.net - glassfish persistence mailing list archive at Nabble.com.