| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Jim Garrison <jim(dot)garrison(at)nwea(dot)org> |
| Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Using CopyManager with pooled JCA connection |
| Date: | 2013-09-12 21:34:48 |
| Message-ID: | alpine.BSO.2.03.1309121725250.8085@ejurka.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Thu, 12 Sep 2013, Jim Garrison wrote:
> >From: Sehrope Sarkuni [mailto:sehrope(at)jackdb(dot)com] Sent: Thursday,
> >September 12, 2013 2:01 PM One other trick is that if you can get
> >anything that implements java.sql.Connection you can usually get to the
> >"raw" connection by first getting the DB meta data object and then
> >getting the original connection from it.
>
> Spring has a decent explanation of in SimpleNativeJdbcExtractor[1].
> Basically you do conn.getMetaData().getConnection()
>
This seems like a dangerous thing to rely on. Not proxying
DatabaseMetaData seems like a bug to me. Yes, the PG driver doesn't do it
currently, but if it did and broke user code that relied on it not
proxying, I wouldn't have a whole lot of sympathy for the user.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Garrison | 2013-09-12 22:07:22 | Re: Using CopyManager with pooled JCA connection |
| Previous Message | Jim Garrison | 2013-09-12 21:11:08 | Re: Using CopyManager with pooled JCA connection |