Re: Hmm. "String nativeSQL(String sql) . . . converts the . . . JDBCSQL grammar into . . . the native form of the statement"

Hi Dan,

I think you gave a reason -- the word you used was um, let's see "legacy" :).

And really, that's pretty much the only reason I can think of -- when you get put in a situation where you have to work with a database you're not allowed to change...

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx>/

On 1/28/2013 1:51 PM, Dan Kimmel wrote:

I still argue that there is no reason for RRN or other form of arrival sequence in relational databases. Do you have any reasons?

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Monday, January 28, 2013 3:30 PM
To: Java Programming on and around the IBM i
Subject: Re: Hmm. "String nativeSQL(String sql) . . . converts the . . . JDBCSQL grammar into . . . the native form of the statement"

On 1/28/13 12:57 PM, Dan Kimmel wrote:

According to Codd and Date, there is no use for a RRN.

Hmm. And according to Niklaus Wirth, all for-loops must run to completion unless stopped by an exception condition (hence the absence of a "LEAVE," and deprecation-from-day-one of "GOTO," in Pascal). Except that Wirth outgrew such nonsense by the time he invented Modula-2 (which does have a "LEAVE," although I don't remember if it's actually called that).

<rolleyes>
--
JHHL

--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.