See interspersed: --- Joe Audette <[EMAIL PROTECTED]> wrote: > If you are saying the user would navigate through > multiple pages updating a table on each page and you > want to treat all the updates collectively as one > transaction, that is a bad idea.
I agree, that is what I am trying to not do. > You want to pass > all the data required for a single transaction in > one request so it can be committed or rolled back as > part of the same request. Exactly what I want to accomplish. > Web pages are generally > stateless unless you are using session state > variables which is not a good idea in terms of > scalability. You don't want to keep transactions > open from page to page. I don't understand this. I assume you are referring to the application session variables (and I'm using PHP). Yes I'm using session variables to collect the data. How am I keeping transactions open ? Since I don't want to do a transaction till the very end. All I'm doing is bringing the data to last stage. After it's all been collected. > > If you have a transaction that updates multiple > tables and you roll it back, it will negate all > changes (inserts, updates, deletes) that occurred > within the transaction. > > Hope that helps, not sure I'm understanding your > question. That's because my question was somewhat convoluted due to me not completely understanding all of it myself. Stuart > Regards, > > Joe Audette > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
