Re: virtual table

From: Richard Huxton <dev(at)archonet(dot)com>
To: Tomasz Myrta <jasiek(at)klaster(dot)net>
Cc: PGSQL-SQL <pgsql-sql(at)postgresql(dot)org>
Subject: Re: virtual table
Date: 2003-06-23 08:54:54
Message-ID: 200306230954.54185.dev@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Monday 23 Jun 2003 9:39 am, Tomasz Myrta wrote:
> Dnia 2003-06-23 10:29, Użytkownik Richard Huxton napisał:
> > Look into views - you'll need to provide triggers to handle the
> > update/inserts.
>
> I think view won't change too much - there is not too much difference for
> this case between creating view and empty table with trigger returning
> null. I was thinking about something more comfortably - table without
> pre-declared columns so I don't have to change table definition when
> pl/pgsql function changes.
>
> Can anyone tell me how triggers work? Do they need to look into table
> column definition to retrieve data?

Hmm - I think your problem is going to come before that. Any time you do an
INSERT, PostgreSQL is going to need to know the types of all the columns
involved.

For this sort of thing, I try to keep all the related bits (initial function,
views, triggers) in the same text-file to encourage me to remember to update
them all together.

It sounds like this table1 is only being used during transfer. Is there any
reason why you aren't just inserting the required rows into table2.

--
Richard Huxton

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tomasz Myrta 2003-06-23 09:09:42 Re: virtual table
Previous Message Tomasz Myrta 2003-06-23 08:39:16 Re: virtual table