No subject
Fri May 2 19:13:14 EDT 2003
"If a connection is in auto-commit mode, then all its SQL statements
will be executed and committed as individual transactions. Otherwise,
its SQL statements are grouped into transactions that are terminated by
a call to either the method commit or the method rollback. "
I see your point about the requirement for multiple open statements but
at least the spec gives a nod to reality by stating that you can "hack"
the requirement for multiple open statements by serializing them (or
something) when the underlying database doesn't easily support the
concept.
>
> > The way freetdsJDBC is currently implemented your
> statements get rolled
> > back if you close them without committing. Essentially the
> user has to
> > treat a statement in freetdsJDBC as they would a
> connection using any
> > other driver. In my mind this nulls any thread safe
> benefit you might
> > have by the strategy that has been adopted so far.
>
> The strategy adopted "so far" has nothing to do with thread
> safeness.
Sorry, thread safety considerations seemed to be implied by your earlier
response. As it turns out JDBC objects are required to be thread safe
anyway.
> It is simply to allow the user to have multiple statements open per
> connection. Thread safeness is an important concern, but it did not
> drive this descision.
>
More information about the FreeTDS
mailing list