Re: Using CopyManager with pooled JCA connection

From: Jim Garrison <jim(dot)garrison(at)nwea(dot)org>
To: "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Using CopyManager with pooled JCA connection
Date: 2013-09-13 22:28:26
Message-ID: 0C723FEB5B4E5642B25B451BA57E27303EE0368C@S1P5DAG3C.EXCHPROD.USA.NET
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

I solved this by writing a wrapper around the Copy API and Connection that locates and invokes the Copy API via reflection.

This allows me to retrieve the Copy API instance appropriate for both the source and destination database connections when those connection objects came from different class loaders.

This is fairly specific to my situation, but if anybody is interested I can share the code.

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Sehrope Sarkuni 2013-09-14 21:19:07 Vagrantfile/VM for PG JDBC Driver Testing
Previous Message David Johnston 2013-09-13 21:21:09 Re: JDBC 9.2: multiple execution of prepared statement-query delivers different double precision results via getString()