Dear Csaba...
OK, I did some tests on my postgres around view trying
to understand the view concept.
Yes, you are absolutely correct. View is my problem
solution.
I only have to equip the "rule" of the view and that's
it.
Thank you very much for your kindness
I really appreciate your genero
On Tue, 2004-07-27 at 09:55, Prabu Subroto wrote:
> PS>and if the view changes, does it also change the
> related record in table "appointment0" and "appointment1"?
Yes, because a view is pretty much just a stored query (Pg does't have
materialised views).
CREATE VIEW apointment0 AS
Prabu,
You should use views for appointment0 and appointment1.
That way when you insert/modify in appointment, the modifications will
automatically show up in the views too.
See also http://www.postgresql.org/docs/7.4/static/sql-createview.html
on how to create a view.
Cheers,
Csaba.
On Tue, 20
But I think, the modification of records to the table
"appointment0" dan "appointment1" must be done
automatically if my program modifies the
"appointment". That's why I think I should use trigger
and function.
Please tell me more detail.
--- Csaba Nagy <[EMAIL PROTECTED]> wrote:
> Prabu,
>
> You
> I want if my program inserted, updated, deleted the
> record of "appointment" than the postgres does the
> syncronization to the corresponded tables
> (appointment0 or appointment1 or both).
Is there a reason you aren't doing this with views?
--
Mike Nolan
---(end of bro
Dear my friends...
I am using SuSE Linux 9.1 and postgres. I am a
beginner in postgres, usually I use MySQL.
I have 3 tables : appointment, appointment0 and
appointment1.
the fields of table "appointment" are as follows:
noapp* (int4):ID Number of appointment (PK)
custid (int4)