Re: NEW + tableOID
| От | Ricardo Bayley |
|---|---|
| Тема | Re: NEW + tableOID |
| Дата | |
| Msg-id | AANLkTinTMX3xie2CVTHfhJ+itnZ5H5i1jsnQQ6e8tVz+@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: NEW + tableOID (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-admin |
Thanks Tom that was exactly what I was looking for.
Do you think that having just 1 table to perform the Full Text Search is a better approach than having 1 master table with child tables, and always querying the Master one ? Which do you believe is faster ?
regards
On Fri, Aug 13, 2010 at 6:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Ricardo Bayley <ricardo.bayley@gmail.com> writes:That might work in an AFTER trigger, but it definitely won't work in a
> I do this with triggers. This issue I have is that the tableoid data cannot
> be used with the NEW keyword. I always get value 0 instead of the actual
> tableoid.
BEFORE trigger, because the NEW row isn't actually part of the table at
that point. You'd probably be better off to rely on the trigger
function TG_RELID parameter instead, anyway.
regards, tom lane
В списке pgsql-admin по дате отправления: