From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Terence Kearns" <terencek(at)isd(dot)canberra(dot)edu(dot)au>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: minor bug in pgAdmin3 when creating views |
Date: | 2003-07-16 14:33:59 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B844B30A@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Thanks, fixed in CVS.
Regards, Dave.
> -----Original Message-----
> From: Terence Kearns [mailto:terencek(at)isd(dot)canberra(dot)edu(dot)au]
> Sent: 16 July 2003 09:52
> To: pgadmin-support(at)postgresql(dot)org
> Subject: [pgadmin-support] minor bug in pgAdmin3 when creating views
>
>
> When attempting to create a view with the comment box populated,
> pgAdmin3 generated the following SQL
>
> CREATE OR REPLACE VIEW global.v_db_classes AS
> select type_id AS db_class_id, title AS db_class
> from global.types
> where cat = 'dbClasses';
> COMMENT ON TABLE global.v_db_classes IS 'This pseudo entity
> is based on
> the types table and contains a list of entities in the database';
>
> The problem is that in the COMMENT ON statement, said view is now
> referred to as a TABLE instead of a VIEW. This produced the
> appropriate
> error. The work-around was to simply copy/paste it into an
> SQL execution
> window and modify the COMMENT ON statement.
>
>
> --
> Terence Kearns ~ ph: +61 2 6201 5516
> IT Database/Applications Developer
> Enterprise Information Systems
> Client Services Division
> University of Canberra
> www.canberra.edu.au
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
http://www.postgresql.org/docs/faqs/FAQ.html
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2003-07-16 14:54:07 | Re: Database Migration Error |
Previous Message | Dave Page | 2003-07-16 14:27:40 | Re: BUG: pgAdmin III View table with empty strings |