Bug #19339 CONVERT_TZ(): overly aggressive in locking time_zone_name table

Submitted: 25 Apr 2006 16:53 Modified: 7 Dec 2006 16:27
Reporter: Paul DuBois Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1 and up OS:
Assigned to: Assigned Account CPU Architecture:Any

[25 Apr 2006 16:53] Paul DuBois 
Description:
This is related to Bug#9953. I would have expected that
the requirement of time_zone_name to be locked by
CONVERT_TZ() to apply only for named time zones.
But CONVERT_TZ() appears to want to lock that table
even for numeric time zones -- shouldn't that be
unnecessary?

How to repeat:
mysql> lock table t read;
Query OK, 0 rows affected (0.16 sec)

mysql> select convert_tz(now(),'+00:00','+01:00');
ERROR 1100 (HY000): Table 'time_zone_name' was not locked with LOCK TABLES
[26 Apr 2006 2:40] MySQL Verification Team 
Thank you for the bug report.
[7 Dec 2006 16:27] Tomash Brechko 
This bug is a duplicate of bug#9953, look for the fix there.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.044 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.