Hello Norbert,
My assumption is: getIndexInfo() delivers no result, if there is only a primary key on the table.If "getIndexInfo()" delivers no result, "getPrimaryKeys()" is not called by the tool, and the primary key cannot be extracted.
If "getIndexInfo()" delivers a result, "getPrimaryKeys()" is called, and the primary key is extracted properly.So, the question is, whether getIndexInfo() should deliver a result if there is only a primary key on a table ...With kind regardsNorbert Mende
your assumption
is what I see too in the trace. But, getIndexInfo is not very well suited
for that, and a primary key is
no index ... (that's
why there are these different methods). I know that Sun's JDBC:ODBC Bridge did
some mixing
here (which is not
good).
I can only
suggest:
- looking again in the
SUN One Studio whether there are some obscure options for CMP fine-tuning that
helps.
- as a last resort,
create an index on the primary key column (but a descending one, as an ascending
is impossible
to create):
CREATE UNIQUE INDEX index_name on table_name (colum_name
DESC)
perhaps this
trick may do it, although it does look at least a bit
ugly.
I suggest of course
asking at some Sun One mailing list / forum or whatever for the reasoning behind
this unusual
behaviour - perhaps it
is just a nasty bug.
Regards
Alexander
Schr�der
SAP DB, SAP Labs
Berlin
