×
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.
For this very reason, most databases force a primary key constraint on every table created unless you jump through some ugly hoops to bypass default behavior. If you don't have a primary key constraint, you should expect every record that conforms to your where clause to be deleted in one DELETE statement. This is expected behavior in some situations. This is all within the specifications for relational databases and SQL-98 specs.
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Monday, January 28, 2013 4:33 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 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?
I think we're speaking at cross-purposes here:
There is indeed no reason for a properly designed database to require RRN access.
But neither is there any reason to expect all databases to be properly designed, with the result that in a general purpose access utility, there is every reason to assume that the database being accessed is NOT properly designed.
--
JHHL
midrange.com
