On Wed, 11 Oct 2000, Aaron Mulder wrote:
> No! No!!!! *PLEASE* do not check the DatabaseMetaData! This can
> be VERY slow - 10 minutes or more - I've seen it! Sometimes I wake up in
> the middle of the night in a cold sweat thinking about that Oracle
> instance, but it was truly horrible and the DatabaseMetaData was too slow
> to be usable. :) Actually, I think I've seen that twice before, at
> different companies, with different horrible databases - but it's too
> common to ignore.
>
> Aaron
I dont have Oracle so I dont know these Problems ;-)))
No, I didnt know that. The Problem was that the wired query in case of
table does not exist caused a SQL error, which killed my transaction
(marked rollback).
Two possible ways to solve it:
1. bring the transaction stuff into the jaws code and use two
transactions for this operation (reuse the old code)
2. Use a general way to obtain the databases metadata and make a
decission bases on that. The j2ee spec (v1.3 section 9.2.2.3) says that
a compatible driver has to implement that, so I thought Oracle does it
in an professional way.
Any ideas appreciated.
regards
Daniel
