Re: Question for the JDBC experts, Re: getPrimaryKeys

On 3/19/13 12:22 PM, Dan Kimmel wrote:

A primary key describes the table's uniqueness constraint and implies no order. As it happens, DB2 for i will build an index corresponding to the primary key simply because that's the fastest way for it to be able to check if there's already an instance of the key in the table. Indexes do have order. Indexes can also be created optimized for ascending or descending order, though most of the time an index can be read as fast backwards as forwards.

You can use DatabaseMetaData.getIndexInfo() against a table and match the resulting list against the primary key meta data to find the (one of the) indexes that match the primary key.

Does that help?

It might. But I'm not entirely sure how to pull it into JDBCR4: it takes two boolean parameters, and I'm not sure how to prototype a boolean parameter to a Java call in RPG.

When I pulled in getPrimaryKeys, I pulled it in thusly:

D getPrimaryKeys...
D PR ExtProc(*JAVA:
D 'java.sql.DatabaseMetaData':
D 'getPrimaryKeys')
D like(ResultSet)
D catalog like(jString) const
D schema like(jString) const
D table like(jString) const

but I see that getIndexInfo has two boolean parameters in addition to the ones for getPrimaryKeys.

Would I pull them into JDBCR4 as type "1N"?

--
JHHL