Bug #25302 893 reduce/reduce conflicts in parser grammar
Submitted: 28 Dec 2006 6:56 Modified: 16 Jan 2007 6:42
Reporter: Antony Curtis Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Compiling Severity:S1 (Critical)
Version:5.1 OS:
Assigned to: Marc ALFF CPU Architecture:Any
Tags: rt_q1_2007

[28 Dec 2006 6:56] Antony Curtis
Description:
When building 5.1 from source, it can be observed that bison reports the following:

conflicts: 282 shift/reduce, 893 reduce/reduce

How to repeat:
just build the 5.1 from bk repository

Suggested fix:
Apply the following patch

===== sql_yacc.yy 1.527 vs edited =====
--- 1.527/sql/sql_yacc.yy       2006-12-27 22:55:20 -08:00
+++ edited/sql_yacc.yy  2006-12-27 22:54:48 -08:00
@@ -9415,7 +9415,6 @@ keyword:
        | TRUNCATE_SYM          {}
        | UNICODE_SYM           {}
         | UNINSTALL_SYM         {}
-        | USER                  {}
        | WRAPPER_SYM           {}
         | XA_SYM                {}
         | UPGRADE_SYM           {}
[28 Dec 2006 7:27] Sveta Smirnova
Thank you for the report.

Veified as described.
[3 Jan 2007 5:16] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/17562

ChangeSet@1.2377, 2007-01-02 22:16:24-07:00, malff@weblab.(none) +2 -0
  Bug#25302 (893 reduce/reduce conflicts in parser grammar)
  
  This fix corrects build issues introduced by WL#3031:
  
  - In the SQL grammar, 'USER' is a SQL 2003 reserved keyword,
  and therefore should not be part of the keyword production.
  
  - In sql/sql_parse.cc, the code for CREATE SERVER and ALTER SERVER
  was not using proper format strings in the DBUG_PRINT statements.
[15 Jan 2007 16:25] Marc ALFF
Merged into 5.1.15
The problem does not exist in 5.0
[16 Jan 2007 6:42] Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

No direct impact on end users, hence nothing to document; closed without further action.