[geeklog-devel] Table locking
vfuria at gmail.com
Sat Jan 22 09:55:54 EST 2005
Just posted the following to the thread.
Assuming your hosting service is making up a lame excuse not to give
you LOCK TABLES privileges there are a couple things you can do:
0. Tell your host that you want "LOCK TABLE" priveleges or you'll take
your business else where, all the excuses I've seen on this thread
seem very lame. Smile
1. Remove all the "LOCK TABLE" "UNLOCK TABLE" SQL calls from
comment.php. This should be okay if you have a low traffice site, but
opens up the possiblity of corruption if two or more users try to save
or delete comments at the same time.
2. Upgrade to InnoDB tables. There is a script in the admin directory
to do this. Then change every instance of "LOCK TABLE XXX" to "START
TRANSACTION" and every instance of "UNLOCK TABLE XXX" to "COMMIT". The
only downside to this is that it is untested and will only work with
InnoDB tables. If anyone tries this let me know how it works.
I appologize to everyone for the problems that the LOCK statements are
causing. They were implemented to improve comment display performance
(which was misserable).
P.S. Dirk, do you want to this to the FAQ?
On Sat, 22 Jan 2005 14:48:30 +0100, Dirk Haun <dirk at haun-online.de> wrote:
> It seems some of our users are still having problems getting their
> hosting service to allow them to lock tables (needed to post comments as
> of Geeklog 1.3.10).
> The excuses from the hosting services I've heard so far are ... less than
> convincing, to put it politely.
> Can our resident database experts try and shed some light on it in this
> thread, please?
> bye, Dirk
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
More information about the geeklog-devel