× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Vern,

We're on V5R4, so I'm using free-form SQL all the time now and trying not to look back. Like most pioneers, though, I seem to be getting a lot of arrows in my back. ;-)

I'm sure it was just an oversight when they did the formatter, since most people don't use the JOIN/ON syntax very often. After all, the STRSQL prompter only tolerates it, rather than properly supporting it.

It looks to me like the variations on JOIN should be treated more or less like CASE, and ON should be treated like AND/OR. I don't know how hard that would be for IBM to do, though, and I'm not allowed access to put in PMRs. Sigh. I'm just hopeful that one of friendly IBM people will notice this.

Thanks for the NiceSQL info. I'll take a look when I get time.

Dave Shaw
Mohawk Industries

----- Original Message -----
From: <vhamberg@xxxxxxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Wednesday, February 20, 2008 1:16 PM
Subject: Re: [WDSCI-L] Free-form SQL auto formatting in SQLRPGLE


Dave

Thanks - had not seen that - don't usually develop to V5R3 these days.

I suspect it is related to not thinking in terms of the JOIN syntax, maybe it'd work if you do JOINs with the WHERE clause - but that is so restrictive.

I gave the wrong name for the SQL formatter - should be NiceSQL and the site is

http://home.broadpark.no/~ihalvor/

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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

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