James Robinson <jlrobins(at)socialserve(dot)com> writes:
> This sort of fix belongs down deep in AbstractJDBC1Statement,
> whereas my hack-ish cache would exist at a layer much higher
> than this,
I didn't say it was easy ;-) ... when we were designing this last year,
Dave gave me to understand that actually using it will take some pretty
significant revisions in the JDBC driver. But the way forward is open,
as far as I know.
regards, tom lane