Michael Schechter, @Filter, @SqlFragmentAlias, and #deduceAliasInjectionPoints were all documented in the user guide under this fix. They also received beefed-up javadocs. That will be included in today's 4.3.1 release, as well as 4.2.9.

I added the "escape" keyword here, but purposefully avoid that as a precedent. Not only is it unreasonable to attempt to automatically handle all ANSI SQL keywords, it's a bad idea. Too many other users frequently use them as table and column name. Suddenly un-aliasing them all, by default, would be a big breaking change. That's exactly why solutions like #deduceAliasInjectionPoints are in place.