From: | Andreas Zeugswetter <andreas(dot)zeugswetter(at)telecom(dot)at> |
---|---|
To: | "'hackers(at)postgresql(dot)org'" <hackers(at)postgreSQL(dot)org> |
Subject: | AW: [HACKERS] crash on new system views |
Date: | 1998-09-16 13:28:11 |
Message-ID: | 01BDE186.A9D137D0@zeugswettera.user.lan.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > I guess it would be nice if views could show the original oid for all
> > non join or single table views.
>
> IMHO, then the oid should be included as part of the view
> definition itself...even on a join operation, having the OID might be
> useful...consider a case where you have a join of two tables such that the
> select is something like:
>
> select a.oid,a.field,b.field where a.field=b.field;
>
> Having a.oid means that later I can just do:
>
> select * from <view> where oid = <oid#>;
>
> But I think the person setting up the view should be the one
> explicitly including the oid value, not the system "guessing"...
While I perfectly understand your argument, I see a disadvantage, that the above
will show the oid column with the select * while on the original table the oid is hidden.
But besides:
regression=> create view tables as select oid, relname as tabname from pg_class;
ERROR: create: system attribute named "oid"
which is perfectly OK I think.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1998-09-16 14:17:50 | Re: [HACKERS] 6.4-BETA1: libpgtcl.so / Tcl version? |
Previous Message | Sferacarta Software | 1998-09-16 13:15:45 | Re[3]: [HACKERS] SERIAL data type |