From: | Jason Tesser <jasontesser(at)gmail(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Found a Bug in latest Driver (I THINK) and pg 8.4 |
Date: | 2010-06-02 10:10:39 |
Message-ID: | AANLkTikawj0Nso2IvyIIY1Gekk0b4DQC3cH22pDepoRB@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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.
On Wed, Jun 2, 2010 at 6:03 AM, Kris Jurka <books(at)ejurka(dot)com> wrote:
>
>
> On Tue, 1 Jun 2010, Jason Tesser wrote:
>
> 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.
>>
>
> 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?
>
> Kris Jurka
>
From | Date | Subject | |
---|---|---|---|
Next Message | Manohar Bhattarai | 2010-06-02 13:40:15 | Re: Not able to connect to postgresql database |
Previous Message | Kris Jurka | 2010-06-02 10:03:30 | Re: Found a Bug in latest Driver (I THINK) and pg 8.4 |