Hi I often have an application which allows a user to edit a record. Even if the user only updates one field all fields are resaved in the database. Its occured to me that this may be inefficient. I wondered if I could store the fields in hidden form fields, check on the update page which fields have changed and only update the fields that have. I also wondered if this would be best done in a stored proc on the datebase side but I imagine that the stored proc would have to call the record, compare the new field values and then update the neccesary field which be more of a performance hit. Does anyone know if this is worth doing or are any performance gains going to be negligble. Also this seems like a feature that databases may already utilise on a low level but i'm not sure.
Comments anyone? Thanks KOla ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
