| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | salah jubeh <s_jubeh(at)yahoo(dot)com> |
| Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: casting behavior of oids and relation names |
| Date: | 2012-05-16 13:32:48 |
| Message-ID: | 23798.1337175168@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
salah jubeh <s_jubeh(at)yahoo(dot)com> writes:
> In some cases when I cast the oid to relation names ('xxxx'::regclass::text) I get schemaname.tablename and in some cases I just get tablename. I thought at thebeginning,this is due name duplication of tables in differentschemasbut it seems not. Also, this seems as a schema option because it happen only in certain schemas. How I can get a consistent names 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gauthier, Dave | 2012-05-16 13:54:23 | maybe incorrect regexp_replace behavior in v8.3.4 ? |
| Previous Message | salah jubeh | 2012-05-16 13:20:56 | casting behavior of oids and relation names |