The development team is looking to improve some functionality with the SQL
automatic formatter and we are seeking your feedback to give us some
guidance. Some of you may have experienced the frustration of pushing
embedded SQL code beyond column 80 while the automatic formatting
preference is turned on. Once the cursor is moved to another line, the
formatter will re-format the SQL statement but leave behind any code pushed
beyond column 80, since anything after this is generally considered a
comment and should be ignored.
We are proposing a solution to have another preference to turn on with the
SQL formatter that will allow SQL that goes beyond column 80 to be
considered part of the statement and not a comment. This will prevent the
formatter from ignoring any code that may get pushed out during a reformat
of the statement.
What we would like to know is how many of you use the space beyond column
80 to write the comments for SQL statements, versus including it directly
in the code (ie: using '//' or '/*' to comment). Also, would this solution
help those who use automatic SQL formatting? If this solution helps, we
would appreciate any recommendations on what the new preference should be
named in order to make its intention obvious to the user.
Software Developer for Rational Developer for i
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.