> Hello,
>
[quoted text clipped - 5 lines]
> thanks,
> Peter
The getMetaData call itself isn't slow, right? Certain DatabaseMetaData
calls can certainly be slow, because some of them can make some complicated
queries.... I don't think there's much you can easily do from the client
to make the metadata querires faster, but if you collect the trace from
the DBMS and examine those queries, your DBA *may* be able to do some
admin stuff to make those queries faster. Other than that, how volatile
is the metadata you're asking for? Can you cache and re-use it?
Good luck,
Joe Weinstein at BEA Systems
Meetlint - 29 Mar 2006 07:38 GMT
>> Hello,
>>
[quoted text clipped - 7 lines]
>
> The getMetaData call itself isn't slow, right?
Right.
Certain DatabaseMetaData
> calls can certainly be slow, because some of them can make some complicated
> queries.... I don't think there's much you can easily do from the client
> to make the metadata querires faster, but if you collect the trace from
> the DBMS and examine those queries, your DBA *may* be able to do some
> admin stuff to make those queries faster. Other than that, how volatile
> is the metadata you're asking for? Can you cache and re-use it?
We are caching it. But actually the information is only used once. :-)
It is sort of a databinding check routine against the database fields.
We are now hiding it behind an interface to experiment with direct
Oracle selects.
> Good luck,
Thanks,
Peter