Re: using composite types in insert/update
От | Sam Mason |
---|---|
Тема | Re: using composite types in insert/update |
Дата | |
Msg-id | 20090130201233.GA3008@frubble.xen.chris-lamb.co.uk обсуждение исходный текст |
Ответ на | Re: using composite types in insert/update (Merlin Moncure <mmoncure@gmail.com>) |
Ответы |
Re: using composite types in insert/update
|
Список | pgsql-hackers |
On Fri, Jan 30, 2009 at 02:47:49PM -0500, Merlin Moncure wrote: > On 1/30/09, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Merlin Moncure <mmoncure@gmail.com> writes: > > > You are missing the point, using the composite type allows you to > > > build the insert without knowing the specific layout of the > > > table... > > > > Surely at *some* level you have to know that. > > You don't (if I understand your meaning) ...you just have to make sure > the destination of the insert is the same as the source. Sounds as though there are at least two levels that know the specific layout of the tables involved then. 1) PG has to know the structure of the tables, and 2) you application relies on the fact that tables of the same name have the same structure. Sounds like a very simple ah-hoc nominal type system to me. -- Sam http://samason.me.uk/
В списке pgsql-hackers по дате отправления: