It looks like there's a bug that allows you to create views with columns of type
unknown, and then prevents you from dropping the view/table.
alpha_2=> \i brokenview
CREATE VIEW article_contrib_info AS
SELECT ac.article_id,
p,firstname, -- TYPO HERE, USED COMMA INSTEAD OF PERIOD
p.lastname
FROM person p, article_contributor ac
WHERE ac.person_id = p.person_id;
NOTICE: create: attribute named "p" has an unknown type
NOTICE: unknown node tag 704 in OffsetVarNodes()
NOTICE: Node is: { IDENT "p" }
NOTICE: copyObject: don't know how to copy 704
CREATE
alpha_2=> \d article_contrib_info
Table = article_contrib_info
+----------------------------------+----------------------------------+-------+
| Field | Type | Length|
+----------------------------------+----------------------------------+-------+
| article_id | int4 | 4 |
| p | unknown | var |
| firstname | varchar() | 0 |
| lastname | varchar() | 0 |
+----------------------------------+----------------------------------+-------+
alpha_2=> drop view article_contrib_info;
ERROR: badly formatted planstring "IDENT "p" "...
alpha_2=> drop table article_contrib_info;
ERROR: badly formatted planstring "IDENT "p" "...
alpha_2=>
Has anyone else heard of this behavior? Is it a documented bug? Or am I missing
something obvious about how to resolve this kind of problem?
Charlie
