Fernando Monteiro wrote:
Hello, Michael,
Version 4.0.15 comes after version 4.0.2 (15 > 2), so the version is not a problem here.
(...)
I asked them to give me the "lock tables" permission, but they answered this permission
option isn't available on versions prior to 4.0.2. They also told me they would have to
give me a high elevated privilege to issue these commands.
It was a typo, sorry... The right version should be 4.0.20.
Thank you for you explanation about the lock table permission !!
Regards,
Fernando Monteiro
You're welcome.
If you look at the quote I included from the manual, the LOCK TABLES privilege has been available since version 4.0.2, so they are wrong if they told you 4.0.20. The next sentence in the manual after the one I quoted is "In MySQL 3.23, you must have SELECT, INSERT, DELETE, and UPDATE privileges for the tables." In other words, the LOCK TABLES global privilege was added in 4.0.2 to further restrict who could lock tables. So, again, the version of mysql is not a problem -- the ability to lock tables has been in mysql for a long time. In fact, prior to 4.0.2 you would most likely have been able to lock tables already, as I imagine you do have SELECT, INSERT, DELETE, and UPDATE privileges on your own tables.
They can give you the ability to lock tables in 4.0.15, if they choose to. If they are your tables, I'm not sure why they are reluctant to do so. The only reason I can think of would be if they have already given you SELECT permission on tables which are not yours, which they don't want you to lock. Now that you are armed with the truth, perhaps you can get them to tell you their real reasons...
Michael
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
