I have to confess I have used the space beyond column 80 for comments at
times--although it's been a while and I doubt that I ever used it on SQL
code. Regardless, I would rather be able to enter and have the SQL
properly automatically format than use the comment area.
I like Barry's suggestion for the preference, "Extend SQL beyond column
80." I might add the word "entry" after SQL for clarity--i.e., "Extend SQL
entry beyond column 80."
It would be great if this worked in COBOL as well. (Yes, there really are
some of us who use COBOL too.)
"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 06/12/2014 02:39:43 AM:
----- Message from "Colson, Edmund B" <Barry_Colson@xxxxxxx> on Wed,Systems
11 Jun 2014 20:04:59 +0000 -----
"'Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries'" <wdsci-l@xxxxxxxxxxxx>
Re: [WDSCI-L] Feedback regarding the automatic SQL Formatter
I, and my team, do not use the space beyond 80 for comments.
You might call the new preference something that says "Extend SQL
beyond column 80". To me that would be simple enough.
Barry Colson | Sr. Programmer, Shared Services | Community Health
4000 Meridian Blvd | Franklin, TN 37067 | Tel: 615.628.6719 | Fax:Morris
615.465.3026 | http://www.chs.net
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Taryn
Sent: Wednesday, June 11, 2014 1:10 PMcolumn
Subject: [WDSCI-L] Feedback regarding the automatic SQL Formatter
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
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.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.