Hi James,
The nativeSQL() method asks the driver for the, um, native SQL version
of the statement submitted.
RRN is not an SQL concept.
Database metadata allows access to all information available, including
SQL conformance. Since JDBC is an SQL API, it doesn't provide info for
things outside the standard. A specific JDBC driver, of course, can do
anything it wants to do, so long as it conforms to the rest of the JDBC
standard.
What, your Chinese guys don't know this?
HTH,
Joe Sam
Joe Sam Shirah - www.conceptgo.com (904) 302-6870
conceptGO - Consulting/Development/Outsourcing
Java Filter Forum: www.ibm.com/developerworks/java
Just the JDBC FAQs: www.jguru.com/faq/JDBC
Going International? www.jguru.com/faq/I18N
Que Java400? www.jguru.com/faq/Java400
-----Original Message-----
From: James H. H. Lampert
Sent: Monday, January 28, 2013 12:16 PM
To: Java Programming on and around the IBM i
Subject: Hmm. "String nativeSQL(String sql) . . . converts the . . . JDBCSQL
grammar into . . . the native form of the statement"
From the JavaDoc:
nativeSQL
String nativeSQL(String sql) throws SQLException
Converts the given SQL statement into the system's native SQL
grammar. A driver may convert the JDBC SQL grammar into its system's
native SQL grammar prior to sending it. This method returns the
native form of the statement that the driver would have sent.
Anybody here know what that's all about? Is there some unified JDBC SQL
standard that somehow homogenizes things like RRN in DB2/400, and LIMIT
in MySQL?
Also, does anybody know of a way, via a JDBC connection, to find out
(other than by trial-and-error) whether a given database system supports
things like RRN and LIMIT, and whether a given table has a primary key?
--
JHHL
midrange.com
