Re: Behaviour of setAutoCommit may not be completely correct.

Ok. I believe you are right.

Looks like postgresql is doing the right thing. I'm gonna pass this
information to the dods developper team.

Many thanks.

Best regards.
João Paulo Ribeiro

Kris Jurka wrote:
>
>
> On Sat, 1 Apr 2006, Tom Lane wrote:
>
>> It looks to me like Sun is trying to clarify their reading of that
>> detail with the javadoc change.  It's a crummy way to handle it; they
>> should have updated the spec.  But I'd say the handwriting is on the
>> wall about what the next spec version will say.
>>
>
> The JDBC 4.0 public draft spec says:
>
> The default is for auto-commit mode to be enabled when the Connection
> object is created. If the value of auto-commit is changed in the
> middle of a transaction, the current transaction is committed. If
> setAutoCommit is called and the value for auto-commit is not changed
> from its current value, it is treated as a no-op.
>
> The JDK1.6 beta2 javadoc confirms this:
>
> NOTE: If this method is called during a transaction and the
> auto-commit mode is changed, the transaction is committed. If
> setAutoCommit is called and the auto-commit mode is not changed, the
> call is a no-op.
>
> So I think we're fine.
>
> Kris Jurka
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
>


--
João Paulo Ribeiro | Senior Software Engineer
jp@mobicomp.com

PHONE: + 351 253 305 250
FAX  : + 351 253 305 250
www.mobicomp.com

________________________________________________________________

About Solutions | Wireless World

CONFIDENTIALITY NOTICE: This message, as well as existing attached files, is confidential and intended exclusively for
theindividual(s) named as addressees. If you are not the intended recipient, you are kindly requested not to make any
usewhatsoever of its contents and to proceed to the destruction of the message, thereby notifying the sender. 
DISCLAIMER: The sender of this message can not ensure the security of its electronic transmission and consequently does
notaccept liability for any fact which may interfere with the integrity of its content.