| From: | "Aasmund Midttun Godal" <postgresql(at)envisity(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | oid's in views. |
| Date: | 2001-10-19 03:01:49 |
| Message-ID: | 20011019030149.23206.qmail@ns.krot.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
CREATE VIEW testview AS SELECT test.oid, tull FROM test;
ERROR: Attribute 'oid' has a name conflict
Name matches an existing system attribute
I think this should be allowed, because if you do:
CREATE VIEW testview AS SELECT tull FROM test;
SELECT oid, tull FROM testview;
The oid column will always be blank. The oid column can never be used for anything usefull.
There are many workarounds to this problem - and I appreciate that altering this behaviour might be contradictory to some design philosophy you may have. Just my comment that's all!
Aasmund Midttun Godal
aasmund(at)godal(dot)com - http://www.godal.com/
+47 40 45 20 46
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bhuvan A | 2001-10-19 06:01:45 | Need a VIEW without SUB-SELECT |
| Previous Message | David Allardyce | 2001-10-19 02:56:53 | Table Constraints with NULL values |