Browse Source

Fixing a type-clash bison warning in keyword_directly_not_assignable

The warning was introduced by the patch that added
the keyword_sp_verb_clause rule.
pull/449/head
Alexander Barkov 8 years ago
parent
commit
31b3511849
  1. 14
      sql/sql_yacc_ora.yy

14
sql/sql_yacc_ora.yy

@ -14796,13 +14796,13 @@ keyword_directly_assignable:
CREATE TRIGGER .. FOR EACH ROW FOLLOWS tr1 a:= 10;
*/
keyword_directly_not_assignable:
CONTAINS_SYM { /* SP characteristic */ }
| LANGUAGE_SYM { /* SP characteristic */ }
| NO_SYM { /* SP characteristic */ }
| CHARSET { /* SET CHARSET utf8; */ }
| FOLLOWS_SYM { /* Conflicts with assignment in FOR EACH */}
| PRECEDES_SYM { /* Conflicts with assignment in FOR EACH */}
| keyword_sp_verb_clause
CONTAINS_SYM { /* SP characteristic */ }
| LANGUAGE_SYM { /* SP characteristic */ }
| NO_SYM { /* SP characteristic */ }
| CHARSET { /* SET CHARSET utf8; */ }
| FOLLOWS_SYM { /* Conflicts with assignment in FOR EACH */}
| PRECEDES_SYM { /* Conflicts with assignment in FOR EACH */}
| keyword_sp_verb_clause { }
;
/*

Loading…
Cancel
Save