Re: Event Triggers reduced, v1
От | Robert Haas |
---|---|
Тема | Re: Event Triggers reduced, v1 |
Дата | |
Msg-id | CA+TgmoZ87pL8bb_Urc7iFN=oiZZF0r3X=XhHRj0eKFo4Sudmow@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Event Triggers reduced, v1 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Event Triggers reduced, v1
|
Список | pgsql-hackers |
On Mon, Jul 2, 2012 at 6:59 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Robert Haas <robertmhaas@gmail.com> writes: >> So let's try to hammer something out now. The obvious thing that >> occurs to me is to have a column in the catalog that is a 2-D array of >> text, with the first element of each array being something like "tag" >> or "subtag" (i.e. event_trigger_variable) and the remaining array >> elements being a list of legal values. That is: > >> WHEN thingy IN thingy IN ('item1', 'item2') AND otherthingy IN ('foo', 'bar') > >> would be represented as this array: > >> {{thingy,item1,item2},{otherthingy,foo,bar}} > > Um, doesn't that require nonrectangular arrays? Or is there some > non-obvious reason why the lists of legal values will always be all the > same length? Doh. You're right: I keep forgetting that arrays have to be rectangular. Any suggestions on a sensible way to represent this? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: