Re: Using Expanded Objects other than Arrays from plpgsql
От | Tom Lane |
---|---|
Тема | Re: Using Expanded Objects other than Arrays from plpgsql |
Дата | |
Msg-id | 3797606.1732045516@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Using Expanded Objects other than Arrays from plpgsql (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: Using Expanded Objects other than Arrays from plpgsql
Re: Using Expanded Objects other than Arrays from plpgsql |
Список | pgsql-hackers |
Pavel Stehule <pavel.stehule@gmail.com> writes: > út 19. 11. 2024 v 18:51 odesílatel Michel Pelletier < > pelletier.michel@gmail.com> napsal: >> A couple years ago I tried to compress what I learned about expanded >> objects into a dummy extension that just provides the necessary >> boilerplate. It wasn't great but a start: >> https://github.com/michelp/pgexpanded >> Pavel Stehule indicated this might be a good example to put into contrib: > another position can be src/test/modules - I think so your example is > "similar" to plsample Yeah. I think we've largely adopted the position that contrib should contain installable modules that do something potentially useful to end-users. A pure skeleton wouldn't be that, but if it's fleshed out enough to be test code for some core features then src/test/modules could be a reasonable home. regards, tom lane
В списке pgsql-hackers по дате отправления: