| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Get TupleDesc for extension-defined types |
| Date: | 2024-09-18 10:11:49 |
| Message-ID: | CAFj8pRCxXEn02XDQed9VdR2=NKnnd1s=jf1J8Yy7nyLTYt=dfw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
st 18. 9. 2024 v 9:04 odesílatel Florents Tselai <florents(dot)tselai(at)gmail(dot)com>
napsal:
> Correct me if I'm wrong,
> but for an extension that defines composite types,
> there's currently no easy way to get a TupleDesc, even for its own types.
>
> Something like
> TupleDesc get_extension_type_tupledesc(const char *extname, const char
> *typname)
>
> Here's a routine I've stolen borrowed from pramsey's code and have been
> using ever since.
>
> Could this be exposed in extension.h ? (probably without the version check)
>
>
Another significant issue - an only name is not a unique identifier in an
extension.
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2024-09-18 10:12:19 | Re: Detailed release notes |
| Previous Message | Pavel Stehule | 2024-09-18 10:09:04 | Re: Get TupleDesc for extension-defined types |