Table locks should only happen when some sort of "major" updating or housekeeping is needed...it's easy enough to use a simple semaphore system "L" in a text field means it's in use for example...but then you need to consider login / session type tables, and utilities to clear erroneous locks...
On Mon, 2003-06-23 at 12:25, Derek Neighbors wrote: > >> > > > Ok, this implies we cannot do multi-user on MySQL > >> > > > >> > > You can't do multi-user with MySQL because of the problems with > >> locking, and because I'm pretty sure that 'real' multi-user > >> installations will need the balance checkpointing which needs > >> stored proceedures. You can probably work around the events issue > >> by sticking them in a table, and polling that table. > >> > > >> > I am still not coninvinced there is any locking problem here. Also, > >> > >> Can you nest table locks in mysql? I thought you couldn't. Can you > >> rollback? i.e. start to make changes and then decide to skip it? > > > > Yes, you can rollback. I don't know about nested table locks offhand. > > In a multi-user system why on earth would you want to lock a table, much > less multiple tables at a time? I would suspect that as a serious design > flaw. > > Derek Neighbors > GNU Enterprise > http://www.gnuenterprise.org > > > > _______________________________________________ > gnucash-devel mailing list > [EMAIL PROTECTED] > http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel -- Dan Means SRS Consulting, Inc. www.srsbackofficeteam.com _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
