The moose likes JDBC and Relational Databases and the fly likes Updating only modified fields Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "Updating only modified fields" Watch "Updating only modified fields" New topic

Updating only modified fields

Sajee Joseph
Ranch Hand

Joined: Jan 17, 2001
Posts: 200
Hello all,
Consider a scenario in which a form with several editable elements are shown to the User. This form has a save button. Now the User makes some changes and clicks on the save button. The usual practise is to save all the elements (rather than the changed ones). I have heard that its a better practice to save only the modified changes. But this approach has several difficulties :
1. Need to detect a change and which element has changed.
2. We will have to use dynamic Queries.
3. Since the Queries are dynamic i will have to use Java Statement objects rather than Prepared Statements.
Please give your thoughts on this. Is is always advisable to update only the modified field? Now that my Update Query keeps changing, will that not have a negative impact that i cannot have the Query parsed and the Query plan ready, since each query will be a new one (in most cases).
Please give your thoughts on this. Is it actually worth Updating only modified fields??
Sajee Joseph
Phil Chuang
Ranch Hand

Joined: Feb 15, 2003
Posts: 251
I guess it really depends on how much overall data there is.
The thing is really more of a consideration of how much time is saved writing all the data with a prepared query compared to writing some of the data with a dynamic query. If this is going to be a user-oriented process, and done one at a time, then I'd say that you probably won't even notice a performance difference. So it'd be a whole lotta work for marginal (if any) gain.
I agree. Here's the link:
subject: Updating only modified fields
It's not a secret anymore!