Re: Reverse engineering problem on views

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: laurie(dot)burrow(at)powerconv(dot)alstom(dot)com
Cc: pgadmin-support(at)postgresql(dot)org, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Subject: Re: Reverse engineering problem on views
Date: 2004-12-10 11:34:15
Message-ID: 41B989B7.9060204@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support pgsql-patches

laurie(dot)burrow(at)powerconv(dot)alstom(dot)com wrote:

> Retrieved view into SQL dialog window using copy SQL option
>
> This gave
>
> -- View: "test_view"
>
> -- DROP VIEW test_view;
>
> CREATE OR REPLACE VIEW test_view AS
> SELECT or0.actvle AS treename
> FROM gnrcitm g
> LEFT JOIN ((gnrcitmothrref g0
> JOIN other_ref r0 ON g0.idntfyrefid = r0.idntfyrefid AND
> r0.catnmeclssid::text = 'Tree Name'::text) or0) ON g.gnrcitmid =
> or0.gnrcitmid;
>
> When executed this gives ERROR: syntax error at or near ")" at character
> 273.

I can confirm this; the backend's pg_get_viewdef will give these
parentheses too much with pretty-print option=true. Quite awkward, since
this option should *suppress* additional parens...

I'll check the backend code.

Regards,
Andreas

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Andreas Pflug 2004-12-10 13:55:01 pg_get_viewdef returns one paren too much
Previous Message Andreas Pflug 2004-12-10 11:04:26 Re: No drop object confirmation

Browse pgsql-patches by date

  From Date Subject
Next Message Andreas Pflug 2004-12-10 13:55:01 pg_get_viewdef returns one paren too much
Previous Message David Fetter 2004-12-09 23:46:37 PL/Perl document patch