Re: Found a Bug in latest Driver (I THINK) and pg 8.4
| От | Jason Tesser |
|---|---|
| Тема | Re: Found a Bug in latest Driver (I THINK) and pg 8.4 |
| Дата | |
| Msg-id | AANLkTikawj0Nso2IvyIIY1Gekk0b4DQC3cH22pDepoRB@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Found a Bug in latest Driver (I THINK) and pg 8.4 (Kris Jurka <books@ejurka.com>) |
| Список | pgsql-jdbc |
Well PSQL respects search_path but given your objections before and the fact that this would be a change I was suggesting that on PG_OBJECT an option be given to set/getTypeSchema() This way if not set it functions as it does now. No change to current usaage BUT if it is set in the PGOBECT then it would be respected.
I think this provides a way of handling the case which PSQL does and doesn't break backwards compatibility.
I think this provides a way of handling the case which PSQL does and doesn't break backwards compatibility.
On Wed, Jun 2, 2010 at 6:03 AM, Kris Jurka <books@ejurka.com> wrote:
On Tue, 1 Jun 2010, Jason Tesser wrote:I'm not sure where you are suggesting that this attribute would live. Are you suggesting we should have a PGConnection method setSearchPath(String) that would set the search path on the server side and make the driver aware of the change? Are you suggesting that PGObject should have a getTypeSchema()? Can you clarify your suggestion?Right in my case my schema changes as each organization has a separate
schema.
I would love to be able to set the schema with the typeName. Why couldn't
that be a seperate attribute in Java setLookupSchema and if not set function
as it does now. Wouldn't this handle both cases.
Kris Jurka
В списке pgsql-jdbc по дате отправления: