Well, that begs the question - will restarting the MySQL server instance
tonight fix
the current problem? We do have a plan in place to test and eventually deploy
a more
recent version of MySQL (5.6?), but for now, I have to support 1000's of
customers.
My fingers are crossed.
On 6/27/13 12:22 PM, Claudio Nanni wrote:
Hi,
On 06/27/2013 08:19 PM, Andy Wallace wrote:
Benjamin -
Unfortunately:
mysql> show global variables like 'timestamp';
+---------------+------------+
| Variable_name | Value |
+---------------+------------+
| timestamp | 1372238834 |
+---------------+------------+
1 row in set (0.00 sec)
And:
mysql> set global timestamp = 0;
ERROR 1228 (HY000): Variable 'timestamp' is a SESSION variable and can't be
used with SET GLOBAL
Then, as Benjamin said, you have found the bug.
'GLOBAL timestamp' should not exist
http://bugs.mysql.com/bug.php?id=49686
Your GLOBAL (ghost) instance of this variable sets the SESSION one at every
client connection.
But you are sort of trapped because there is no syntax to manipulate that
GLOBAL instance.
Also, sadly the manual page does not explain what happens if you set it to
DEFAULT:
http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html
Cheers
--
Andy Wallace
iHOUSEweb, Inc.
awall...@ihouseweb.com
(866) 645-7700 ext 219
--
"Sometimes it pays to stay in bed on Monday, rather than spending the rest of the
week debugging Monday's code."
- Christopher Thompson
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
