13 Feb 2003 8:39 pm, Manfred Koizar wrote:
> On Thu, 13 Feb 2003 18:28:50 +0100, Nicholas Allen
>
> <[EMAIL PROTECTED]> wrote:
> >Because the WHERE clause is directly affected by the ORDER BY clause.
>
> No, it's not (at least in your query).
>
> > If you
&g
,
On Thursday 13 Feb 2003 4:17 pm, Tom Lane wrote:
> Nicholas Allen <[EMAIL PROTECTED]> writes:
> > I then commented out the line just to see if this would fix the problem.
> > Then I rebuilt it started the server up and connected. I performed the
> > count query as I de
the rows
that would be returned in the query? Is this a bug in Postgres and is there a work
around? I am using Postgres 7.3.
Thanks again!
On Wednesday 12 Feb 2003 11:45 pm, Dmitry Tkach wrote:
> Nicholas Allen wrote:
> >Ok I thought of that but what happens if there is no primary key in
base views.
On Wednesday 12 Feb 2003 9:37 pm, Bruno Wolff III wrote:
> On Wed, Feb 12, 2003 at 20:55:21 +0100,
>
> Nicholas Allen <[EMAIL PROTECTED]> wrote:
> > I thought of this but the problem is that there may be multiple rows with
> > the same value for the column I
ected and scroll to that location.
Any help would be very much appreciated.
Thanks in advance,
Nicholas Allen
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTE
