Yes, that plus Richard's comments were very helpful... I now clearly understand. (See my comments to Richard) Thanks... Jim
on 3/17/04 11:56 AM, Jan Schenkel wrote: > --- Jim Carwardine > <[EMAIL PROTECTED]> wrote: >> When I think of a transaction I think of updating >> data to the database. >> Does this mean that the Classic version only >> supports queries, but can >> support multiple user queries, where Pro supports >> multiple user updates as >> well? Jim >> > > A transaction is a set of database changes that needs > to be treated as one operation : either they all > succeed, or they all fail. > So suppose you're updating a series of records, and > somewhere along the way you notice that something is > not as expected : to undo the changes you've made so > far, you can 'rollback' the transaction. > Does that make more sense ? > > In conclusion, if MySQL Classic doesn't support > transactions, that means you can't 'rollback' your > changes halfway down the road ; MySQL Pro, using > InnoDB databases, does allow you to 'rollback' these > changes. > > Hope this clarified it a bit, > > Jan Schenkel. > > ===== > "As we grow older, we grow both wiser and more foolish at the same time." (La > Rochefoucauld) > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - More reliable, more storage, less spam > http://mail.yahoo.com > _______________________________________________ > use-revolution mailing list > [EMAIL PROTECTED] > http://lists.runrev.com/mailman/listinfo/use-revolution -- OYF is... Highly resourceful people working together. <http://www.OwnYourFuture-net.com> Own Your Future Consulting Services Limited, 1959 Upper Water Street, Suite 407, Halifax, Nova Scotia. B3J 3N2 Info Line: 902-823-2477, Phone: 902-823-2339. Fax: 902-823-2139 _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
