Re: casting behavior of oids and relation names - Mailing list pgsql-general

From Tom Lane
Subject Re: casting behavior of oids and relation names
Date
Msg-id 23798.1337175168@sss.pgh.pa.us
Whole thread Raw
In response to casting behavior of oids and relation names  (salah jubeh <s_jubeh@yahoo.com>)
List pgsql-general
salah jubeh <s_jubeh@yahoo.com> writes:
> In some cases when I cast the oid to relation names ('xxxx'::regclass::text) �I get �schemaname.tablename and in some
casesI just get tablename. I thought at the�beginning,�this is due name duplication of tables in different�schemas�but
itseems not. �Also, this seems as a schema option because it happen only in certain schemas. �How I can get a
consistentnames of the casting ?� 

That's a feature, not a bug --- it doesn't qualify the name if
qualification is unnecessary given your current search_path.

For user tables, you could force it to always qualify by setting
search_path to empty, I think.

            regards, tom lane

pgsql-general by date:

Previous
From: salah jubeh
Date:
Subject: casting behavior of oids and relation names
Next
From: Vibhor Kumar
Date:
Subject: Re: casting behavior of oids and relation names