On 17/01/2017 10:40, Mark Rotteveel wrote: > On 2017-01-17 12:09, Dmitry Yemanov wrote: >> 17.01.2017 13:57, Adriano dos Santos Fernandes wrote: >>> Yep? Ok to break lots of applications? >> We cannot make all the new tokens non-reserved, it's practically >> impossible. BINARY/VARBINARY are standard and reserved per SQL spec, so >> affected users will have to adjust their databases. Life is so cruel. > It should be possible to add one or more alternative rules in the > grammar where character set names are used in a way that preserves the > backwards compatibility. > > I believe this is the thing we need to do.
Just something as "identifier | BINARY" rule. We're not talking about a random word that become reserved, but a word that Firebird itself defined to be used in this way. Adriano ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
