https://bugs.eclipse.org/bugs/show_bug.cgi?id=373332
PL/SQL Package or object types containing keywords breaks Oracle DDL parser
Change parser so that keywords can also be used as identifiers
NB: had to add 2 keywords (CONSTRAINT, PRIMARY) to the list of reserved
words that cant be identifiers - it is not exactly 100% compliant to
the appendix http://docs.oracle.com/cd/E11882_01/appdev.112/e25519/fundamentals.htm#CBJGBIGI
Everytime I tried to include those keywords, the generated parser de-volved
into a morass of ambiguous productions could not resolve 'normal' DDL
let alone DDL that includes a keyword.
I don't think adding CONSTRAINT and PRIMARY is too much
14 files changed
