You can use "logical lock" - set a STATUS int <>0 (probably the ID of user) to indicate someone started to edit it interactively to block other user to edit the same record. Before you write it back to disk, read it again in a buffer to keep all data possible changed by batch updates. Or separate the table to 2 tables, one for each kind of update. Also I use a kind of "transactions" before I know that exists, I don't subtract from "items" directrly but I put it in a field named "keeps". If user change his mind or something goes wrong, I only subtruct from "keeps" fields.Otherwise I subtract from "items" and "keeps". Of course I have create another temp file with the invoice. I use these methods several years now mainly with C-tree from Faircom, they work fine. But to tell you the true, I use Delphi with Interbase for this kind of application on the net. I don't know if it's possible with PHP.
Can someone directs me to the avantages of Inno base comparing wtih default MySQL? Row locking is the bigest one as I can read here? Thanks Makis > -----Original Message----- > From: Tobias Lind - Telia Internet [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 05, 2002 2:46 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: InnoDB frightens me... > > > Thanks - that would be great! > I'm sure a lot of people will find this very helpful. > > Regards, > Tobias > > > ----- Original Message ----- > From: "Michael Widenius" <[EMAIL PROTECTED]> > To: "Tobias Lind - Telia Internet" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Tuesday, March 05, 2002 12:36 PM > Subject: Re: InnoDB frightens me... > > > > > > Hi! > > > > Tobias> Hi! > > Tobias> I'm in the same position as Steve: Considering > switching from MyISAM to InnoDB because of > the > > Tobias> row-level locking capabilities. My application has > quite a lot of updates/inserts mixed > with > > Tobias> selects, and is starting to suffer from the > table-locking policy... > > Tobias> And like Steve, I'm also scared! :) > > > > <cut> > > > > Tobias> Maybe some of this confusion and fear could be > avoided with a section in the InnoDB > documentation > > Tobias> that describes InnoDB from a "MyISAM-point-of-view" :) > > > > Tobias> Explaining how all common things, principles and > routines with MyISAM works with InnoDB. > I'm sure a > > Tobias> lot of people have very good knowledge of MyISAM > and comes from the same direction as I > do... > > > > I have forwarded this to our docmentation team and we shall > try to do > > this in the near future. > > > > Regards, > > Monty > > > > -- > > For technical support contracts, goto https://order.mysql.com/ > > __ ___ ___ ____ __ > > / |/ /_ __/ __/ __ \/ / Mr. Michael Widenius > <[EMAIL PROTECTED]> > > / /|_/ / // /\ \/ /_/ / /__ MySQL AB, CTO > > /_/ /_/\_, /___/\___\_\___/ Helsinki, Finland > > <___/ www.mysql.com > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail > <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
