| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Quartz <quartz12h(at)yahoo(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JDBC gripe list (the autocommit subthread) |
| Date: | 2011-04-06 21:35:08 |
| Message-ID: | BANLkTinoJRSK70Y3r-fgOH2xgHO2h0_bEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Hi Quartz
I think at this point your best option is to change the driver
yourself, and send a patch to the list, because there doesn't seem to
be anyone else who agrees with your interpretation of the spec (and so
it's unlikely to get built by anyone else)
You'll need to justify the behavioral/performance changes that your
patch causes - for example, we wouldn't want existing apps to suddenly
slow down because they're doing 100x the previous number of
transactions. I'd suggest making it a configurable connection option,
defaulting to off, to avoid that problem.
Oliver
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Lister | 2011-04-06 21:51:46 | Recommended resource type and settings for J2EE/Glassfish connection pool |
| Previous Message | Quartz | 2011-04-06 16:11:19 | Re: JDBC gripe list (the autocommit subthread) |