From: | Bartosz Dmytrak <bdmytrak(at)eranet(dot)pl> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: ENUM type script in pgAdmin 1.14.0 |
Date: | 2011-09-27 18:47:35 |
Message-ID: | CAD8_UcYP3+Ee3WSLKC9z934hTOUgDt43trO_szxgFANLtiCqMA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
I made double check (both Win and Linux).
This time everything is OK - schema name is included in script.
This is a little strange for me, because previous script has been copied
from script output (without schema name). Right now I cannot reproduce this
bug(?) again.
Thanks for Your time.
Regards,
Bartek
2011/9/26 Guillaume Lelarge <guillaume(at)lelarge(dot)info>
> On Mon, 2011-09-26 at 09:33 +0200, bdmytrak(at)eranet(dot)pl wrote:
> > My search_path is set to "$user", pg_temp
>
> I tried, and it works for me. I see the public schema in the definition
> of my type.
>
> Best thing to do is open the query tool, and launch "show search_path".
> And I'm pretty sure you'll find the public schema in it.
>
> > so I think script should contain full definition regardles search_path
> settings (which could change during DB life cycle).
>
> Yes and no. We could add an option to always view the schema, regardless
> of the search_path setting. But one should be able to enable/disable
> this behaviour.
>
>
> --
> Guillaume
> http://blog.guillaume.lelarge.info
> http://www.dalibo.com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bob Vandy | 2011-09-28 23:04:35 | pgadmin3 -- adding CHECK constraint |
Previous Message | Guillaume Lelarge | 2011-09-27 07:14:35 | Re: dlgType.cpp - set connection missing |