Re: [HACKERS] Namespace of array of user defined types is confused by the parser in insert? - Mailing list pgsql-general

From Andrew Dunstan
Subject Re: [HACKERS] Namespace of array of user defined types is confused by the parser in insert?
Date
Msg-id 4F957EC7.4080504@dunslane.net
Whole thread Raw
Responses Re: [HACKERS] Namespace of array of user defined types is confused by the parser in insert?  (Krzysztof Nienartowicz <krzysztof.nienartowicz@gmail.com>)
List pgsql-general
[redirected to pgsql-general]


On 04/23/2012 09:42 AM, Krzysztof Nienartowicz wrote:
> Hello,
> Sorry for re-posting - I initially posted this in pgsql.sql - probably
> this group is more appropriate.


pgsql-general probably would be best. -hackers is for discussion of
internals and development, not for usage questions.


[types have namespaces]

> Is there any way of avoid this error different than having a single
> type defined for all schemas?
> Any hints appreciated..


Probably your best bet is to put the types explicitly in the public
namespace when they are created, instead of relying on the search path
that happens to be in force at the time:

    create type public.foo as ( ...);


Then, assuming that public is in your search path they will be picked up
properly when used. Alternatively, you can namespace qualify them when used:

    create type public.bar as (f1 public.foo[], ...);



cheers

andrew

pgsql-general by date:

Previous
From: Vincenzo Romano
Date:
Subject: Re: How to convert BYTEA (from decrypt) to TEXT?
Next
From: Nick Apperson
Date:
Subject: Chaining inserts ... This would be cool