On Wed, 11 Oct 2000, Aaron Mulder wrote:
> I don't think Oracle has necessarily implemented it in a
> non-professional way. It's just that the DBs get so damn big! When you
> start taking about dozens or hundreds of users with dozens or hundreds of
> tables and corresponding other DB objects - well, it just takes a long
> time to load it all, or transfer it over the network, or whatever.
Well, and when you do a user query over dozens of tables?!
I dont see the point that his has to be a heavy operation!
My query only returns 0 or 1 row with 5 columns!!!
> How does the transaction get marked for rollback? I don't see the
> code that does that - we handle the SQLException directly from the
> PreparedStatement, so what can intervene to mark the transaction for
> rollback? Only Minerva, I would think, but I don't believe it does.
I dont know either. I just said TransactionManager.begin ()
before store.init (), which creates a Transaction with status=active
and after return of store.init() I check the Transaction state again:
state=marked as rollback ?!
> Regardless of what the spec says, I don't think DatabaseMetaData
> is the right solution. Let's try to avoid marking it for rollback, and
> then we should be fine.
Why, when it even works with Hypersonic, InstantDB, Postgres,...
\Daniel
