Re: Feedback regarding the automatic SQL Formatter

Please, please, please don't forget about that poor little brother to RPG that is sitting in the corner all neglected. Of course I refer to COBOL!

I spend a lot of time reformatting SQL statements I have proved work in Data Studio just to make sure it doesn't go over column 72 when pasting it into my COBOL source.

We, as a company, don't use right hand side comments.

Please can you make sure that any solution works for both RPG and COBOL.

Best regards,
Mark

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Edmund Reinhardt
Sent: 12 June 2014 22:21
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Cc: WDSCI-L
Subject: Re: [WDSCI-L] Feedback regarding the automatic SQL Formatter


Actually supporting RPG (and SQL) code before column 8 and after column 80 is a known RPG compiler enhancement. Once that is supported, RDi will follow suite.

In this enhancement the SQL will end up formatted before column 80, but if you happen to type beyond column 80, it will get pulled in an formatted for you. So there is no change to what the compiler considers code or comment.



Regards,

Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i



Phone: 1-905-413-3125 | Home: 1-905-854-6195 IBM
E-mail: edmund.reinhardt@xxxxxxxxxx
RDi YouTube: 8200 Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham, ON L6G 1C7
Find me on: LinkedIn: Canada
http://ca.linkedin.com/in/edmundreinhardt/






From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>,
Date: 12/06/2014 05:14 PM
Subject: Re: [WDSCI-L] Feedback regarding the automatic SQL Formatter
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



Hey, I'd like us to be able to extend everything codewise past column 80!

I think that's a request - and RFE - already.

Maybe that would have to be a global setting, so that all comments would have to be in the regular section of code.

I wouldn't mind that - if one wanted, they COULD put comments on the right this way, too.

Vern

On 6/12/2014 3:58 PM, MichaelQuigley@xxxxxxxxxx wrote:

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,
11 Jun 2014 20:04:59 +0000 -----

To:

"'Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries'" <wdsci-l@xxxxxxxxxxxx>

Subject:

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.



Regards,



Barry Colson | Sr. Programmer, Shared Services | Community Health

Systems

4000 Meridian Blvd | Franklin, TN 37067 | Tel: 615.628.6719 | Fax:
615.465.3026 | http://www.chs.net

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
Taryn

Morris

Sent: Wednesday, June 11, 2014 1: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.

________________________________

“**Confidentiality**
The information contained in this e-mail is confidential, may be privileged and is intended solely for the use of the named addressee. Access to this e-mail by any other person is not authorised. If you are not the intended recipient, you should not disclose, copy, distribute, take any action or rely on it and you should please notify the sender by reply. Any opinions expressed are not necessarily those of the company.

We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you.