| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
| Cc: | "Vitaly Belman" <vitalyb(at)gmail(dot)com>, <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgadmin-support] Schemas causing problems :( |
| Date: | 2004-07-27 13:33:45 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E41A748A@ratbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 27 July 2004 16:16
> To: Dave Page
> Cc: Vitaly Belman; pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] [pgadmin-support] Schemas
> causing problems :(
>
> Complicated.
> Before trying to suppress the schema, I'm checking for any
> duplicate type names now. If so, schema is always emitted. In
> your sample:
> pg_catalog.text and public.text.
OK, that should work as well. Probably safer too I guess, though it is
vaguely possible that a schema name be unnecessarily included - a small
price to pay.
/D
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2004-07-27 15:16:08 | Re: [pgadmin-support] Schemas causing problems |
| Previous Message | Dave Page | 2004-07-27 12:34:54 | Re: [pgadmin-support] Schemas causing problems :( |