You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it is now, some proprietary SQL features are not supported, like FOR XML PATH() on SQL Server for example.
As long as it would be nice to eventually have such language support, if the ast object was at least keeping the original SQL comments, it would be possible to us to pre-parse the sql text, transform unknown tags for the parser into comments, and later when rebuilding the sql, either revert back those comments to normal tags or even do custom replacements based on some arbitrary logic.
This would make a lot easier to live with parser limitations.
Thanks!
The text was updated successfully, but these errors were encountered:
The underlying parser, https://github.com/pegjs/pegjs, has functionality in its main branch to return comments back into the AST. Unfortunately, it is not (yet) part of the latest released version, and it has been a while since there was activity in that repo.
As it is now, some proprietary SQL features are not supported, like FOR XML PATH() on SQL Server for example.
As long as it would be nice to eventually have such language support, if the ast object was at least keeping the original SQL comments, it would be possible to us to pre-parse the sql text, transform unknown tags for the parser into comments, and later when rebuilding the sql, either revert back those comments to normal tags or even do custom replacements based on some arbitrary logic.
This would make a lot easier to live with parser limitations.
Thanks!
The text was updated successfully, but these errors were encountered: