This sounds like an excellent feature.

I generate code (SELECT, UPDATE, INSERT) with field descriptions as
comments and the column 80 limitation causes problems. IMO, lifting the
column 80 barrier would help during entry in almost every case. Even a
simple SELECT can take 60 characters or more, and pressing ENTER on an
incomplete statement without a semicolon makes a bit of a mess (I'll be
grateful if there's a secret to avoiding this problem).

It would be nice if RDi would wrap automatically during entry if a
statement extended past column 80. An alternate solution is to allow a
(manual) new line so entry can continue and without attempting to complete
the incomplete statement by appending the next line with valid code. It
would be great if we could type *any* free-form statement (SQL or DDS)
beyond column 80 and have RDi wrap it based on autoformatting rules.

I don't know the costs of changing RDi versus changing the compiler but it
seems that a design goal should be zero impact on the compiler (Barbara
Morris will thank you). I think the right solution is to allow "unlimited"
entry and let RDi autowrap.

Names: "extended line", "SQL autowrap", "virtual statement".

On Wed, Jun 11, 2014 at 11:09 AM, Taryn Morris <tarynmor@xxxxxxxxxx> wrote:

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.


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,
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.