Re: BUG #4618: nolock changes first column name of query result set to 'nolock'

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: brian <b4kramer(at)yahoo(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4618: nolock changes first column name of query result set to 'nolock'
Date: 2009-01-16 12:22:48
Message-ID: 49707C18.5070201@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

brian wrote:
> The following bug has been logged online:
>
> Bug reference: 4618
> Logged by: brian
> Email address: b4kramer(at)yahoo(dot)com
> PostgreSQL version: 8.3.5 build1400
> Operating system: windows xp
> Description: nolock changes first column name of query result set to
> 'nolock'
> Details:
>
> query1 works fine, first column in table is called movieid1:
> select * from netflix.ratings where movieid = 1
>
>
>
>
> query2 is a bug and should work just fine, but gives error:
> ERROR: column "movieid" does not exist
> LINE 2: select * from netflix.ratings with (nolock) where movieid = ...

I don't know where you got "with (nolock)" from, but that's not
PostgreSQL syntax - and AFAIK it's not standard SQL at all. Just remove
it and you should be fine.

//Magnus

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Fuhr 2009-01-16 13:20:51 Re: BUG #4618: nolock changes first column name of query result set to 'nolock'
Previous Message Tom Lane 2009-01-16 03:24:36 Re: pg_listener entries deleted under heavy NOTIFY load only on Windows