Re: Feedback regarding the automatic SQL Formatter

The last time I saw source with comments in the 80+ range, they were
literally punch cards

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael
Ryan
Sent: Thursday, June 12, 2014 8:01 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries
Subject: Re: [WDSCI-L] Feedback regarding the automatic SQL Formatter

Never use column 80 and beyond for comments.


On Thu, Jun 12, 2014 at 8:58 AM, Kurt Anderson <Kurt.Anderson@xxxxxxxxxxxx>
wrote:

Hi Taryn,

We never use columns 80+ for comments.

Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery
Platform

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Taryn
Morris
Sent: Wednesday, June 11, 2014 2:10 PM
To: wdsci-l@xxxxxxxxxxxx
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
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.

Regards,

Taryn Morris
Software Developer for Rational Developer for i
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.