From: | "Aasmund Midttun Godal" <postgresql(at)envisity(dot)com> |
---|---|
To: | joel(at)joelburton(dot)com |
Cc: | josh(at)agliodbs(dot)com, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: oid's in views. |
Date: | 2001-10-21 22:12:55 |
Message-ID: | 20011021221255.1542.qmail@ns.krot.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
That is what i did...
Regards,
Aasmund
On Sat, 20 Oct 2001 23:34:44 -0400 (EDT), Joel Burton <joel(at)joelburton(dot)com> wrote:
> On Sun, 21 Oct 2001, Aasmund Midttun Godal wrote:
>
>
>
> Aasmund --
>
> If your problem is that you want to update VIEWs and aren't sure what the
> PK for the view is, could you follow a standard like this:
>
> CREATE TABLE person (social_security CHAR(9), full_name TEXT);
>
> CREATE VIEW pers_view AS select social_security AS primkey,
> social_security,
> full_name);
>
> and know that you can always find the "primkey" field in the view as one
> to use in where clauses for updates?
>
> HTH,
> --
>
> Joel BURTON | joel(at)joelburton(dot)com | joelburton.com | aim: wjoelburton
> Independent Knowledge Management Consultant
>
Aasmund Midttun Godal
aasmund(at)godal(dot)com - http://www.godal.com/
+47 40 45 20 46
From | Date | Subject | |
---|---|---|---|
Next Message | Aasmund Midttun Godal | 2001-10-21 22:26:03 | Re: CREATE RULE ON UPDATE/DELETE |
Previous Message | Stefan Lindner | 2001-10-21 19:51:47 | Re: system maintained keys |