Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: JDBC: Connection object's Autocommit value for SELECT

Re: JDBC: Connection object's Autocommit value for SELECT

From: Andre van Winssen <andrew_at_info.nl>
Date: Mon, 15 Apr 2002 20:48:04 +0100
Message-ID: <a9faps$3te$1@news1.xs4all.nl>


Thanks sofar, I'll explain further:

> what is a DML ?

that is something like INSERT/UPDATE/DELETE, anything that changes persistent data
but without doing an implicit COMMIT (like CREATE/ALTER statements do)

>>Well, actually no. Oracle does not hold locks if you perform a select,
>>so the commit is just ignored.

About the locks you are right, as far as Oracle is concerned. The impact in oracle exists though,
that's my point. I get these wait events because, I suspect, of the number of commits caused by the
default JDBC driver behaviour.

>>Yes, that means that you have to less rollback segments, or they are
>>too small.

I'm sorry to say, but this is nonsense

>>Why not using Stored Procedure and forget about DML statements at all ?
>>You DO have an Oracle Db ? Then use it!

I know, it's just that this application is not written for Oracle alone, it's supposed to be
database independent. You know, there's more databases than just oracle!

Regards,
Andre van Winssen

"Joe" <yohan1701_at_nospam.space.com> schreef in bericht news:MPG.1724f0ae5eb9c89b989809_at_news.bellglobal.com...
> davide_speed_at_davidebianchi.net scratched out
> > Why not using Stored Procedure and forget about DML statements at all ?
> >
> what is a DML ?
> --
> Joe
>
> "I bent my wookie" - Ralph Wiggum
Received on Mon Apr 15 2002 - 14:48:04 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US