This week's book giveaway is in the JavaScript forum.
We're giving away four copies of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js and have Paul Jensen on-line!
See this thread for details.
Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Strategies for handling updates in existing JPA persistence classes  RSS feed

 
The Wandering Buddha
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

Good Afternoon.

We are doing a project in which we have planned to use JPA Persistence. We think that once the project goes live, there is a small chance that changes in the data model might be required.

My query is that what are the different strategies available to handle such a change. Particularly I have following questions:

1. With updated JPA classes, what are the best practices to incorporate them in the existing database schema?

2. With JPA, are there any best practices to, archive old data, update database schema, and again migrate the database to the new schema?

3. What are the various kinds of changes (broadly speaking) that will make such a migration impossible?

Thanks and Love to all
Ravi
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!