From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dario Teixeira <darioteixeira(at)yahoo(dot)com> |
Cc: | John DeSoi <desoi(at)pgedit(dot)com>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Information about columns |
Date: | 2009-06-23 01:33:52 |
Message-ID: | 19323.1245720832@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dario Teixeira <darioteixeira(at)yahoo(dot)com> writes:
> *However*, if I create a new type (which has an associated pg_class entry),
> and define a function which returns a SETOF that type, RowDescription will
> not tell me its OID. For example:
> ...
> Is this a bug or a conscious decision?
It's intentional; IIRC, the current behavior is defined that way because
that's what the JDBC driver needs to implement the JDBC specs. Putting
information about composite types where information about tables is
expected would confuse the heck out of existing client code.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2009-06-23 01:44:10 | Re: Replication |
Previous Message | Gerry Reno | 2009-06-23 01:29:22 | Re: Replication |