I am waiting for this thread to conclude before deciding exactly what to do for the jdbc driver for 7.3. While using the 'set autocommit true' syntax is nice when talking to a 7.3 server, the jdbc driver also needs to be backwardly compatible with 7.2 and 7.1 servers. So it may just be easier to continue with the current way of doing things, even in the 7.3 case.
thanks, --Barry Curt Sampson wrote: > On Mon, 9 Sep 2002, Tom Lane wrote: > > >>If autocommit=off really seriously breaks JDBC then I don't think a >>simple SET command at the start of a session is going to do that much >>to improve robustness. What if the user issues another SET to turn it >>on? > > > You mean, to turn it off again? The driver should catch this, in theory. > > In practice we could probably live with saying, "Don't use SET > AUTOCOMMIT; use the methods on the Connection class instead." > > Probably the driver should be changed for 7.3 just to use the server's > SET AUTOCOMMIT functionality.... > > cjs ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
