From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'fred(at)ontosys(dot)com'" <fred(at)ontosys(dot)com>, pgadmin-support(at)postgresql(dot)org |
Subject: | RE: 'order by' clause lost when creating view |
Date: | 2001-08-29 08:52:44 |
Message-ID: | 8568FC767B4AD311AC33006097BCD3D61A2DD1@woody.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: fred(at)ontosys(dot)com [mailto:fred(at)ontosys(dot)com]
> Sent: 28 August 2001 13:17
> To: pgadmin-support(at)postgresql(dot)org
> Subject: [pgadmin-support] 'order by' clause lost when creating view
>
>
> When I created a view in pgAdmin II using a SELECT statement
> that includes an ORDER BY clause, pgAdmin seemed to ignore
> that clause. The generated SQL shown with the view properties
> clearly does not have that clause, even though the original
> SQL as shown in the description area does have that clause.
> The same view definition works fine when I create it directly in psql.
>
> Why does pgAdmin translate the view definition SELECT
> statement into a different form, rather than using it verbatim?
>
> This is happening in version 1.1 build 26.
Fred,
I looked at this as promised and the view definition you enter is passed
verbatim to the odbc driver via ADO's Connection.Execute method (what you
see in the logs will be stripped of CRLFs though). Can you send me an
example of what's going wrong for you please - I'd need the definitions of
the underlying tables/functions and the view you are trying to create.
Thanks, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2001-08-31 08:59:14 | pgAdmin II 1.1.28 Released |
Previous Message | Marc G. Fournier | 2001-08-29 03:44:16 | List archives moved and cleaned up ... |