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
When the parser is used to translate SQL scripts (e.g. via the ParserCLI or website), it is often desirable to not touch any comments that may be used to describe parts of the script, e.g.
-- ==========================================-- header-- created 2000-01-01-- ==========================================-- Change Request #14813-- ------------------------------------------CREATETABLEx123 (i int);
CREATETABLEx456 (j int);
-- Special tableCREATETABLEx789 (k int);
-- Change Request #153819-- ------------------------------------------ALTERTABLE x789 ADD x int;
All the whitespace and comments that are located in between statements could be parsed and retained by jOOQ's parser. For now, it would still be difficult to retain comments within a statement as our query object model doesn't allow for representing arbitrary whitespace and comments, but on the top level, that could work.
The text was updated successfully, but these errors were encountered:
When the parser is used to translate SQL scripts (e.g. via the
ParserCLI
or website), it is often desirable to not touch any comments that may be used to describe parts of the script, e.g.All the whitespace and comments that are located in between statements could be parsed and retained by jOOQ's parser. For now, it would still be difficult to retain comments within a statement as our query object model doesn't allow for representing arbitrary whitespace and comments, but on the top level, that could work.
The text was updated successfully, but these errors were encountered: