Store the data in a temporary structure in memory and then write it to the DB once the uploads are finished.
mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog/ On 14 May 2010 17:23, Paolo Broccardo <ad...@cheekyonline.com> wrote: > > >i would start by taking the file upload/processing out of transaction > >if you have it there. > >leave only db insert/update in the transaction. > > > >Azadi > > > >On 14/05/2010 13:20, Paolo Broccardo wrote: > >> > > Hi Azadi - thanks for the feedback. I really like your idea of not having > the uploading in the transaction and have in fact thought about how to do > this before. > > I could remove some processing out of the transaction processing, but the > photo uploading will need to be in the transaction. The reason for this is > that the ID of each inserted album photo is used as the photo filename. > Thus, if uploading 10 photos and photo number 7 fails, the system needs to > roll back all photos already added to the database. If it's not in a > transaction, I can't do this. Unless there is another way I am not thinking > of. > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:333690 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
