Re: BUG #4618: nolock changes first column name of query result set to 'nolock'
От
Magnus Hagander
Тема
Re: BUG #4618: nolock changes first column name of query result
set to 'nolock'
Дата
Msg-id
49707C18.5070201@hagander.net
Ответ на
Список
Дерево обсуждения
BUG #4618: nolock changes first column name of query result set to 'nolock' "brian" <b4kramer@yahoo.com>
Re: BUG #4618: nolock changes first column name of query result
set to 'nolock' Magnus Hagander <magnus@hagander.net>
Re: BUG #4618: nolock changes first column name of query
result set to 'nolock' Michael Fuhr <mike@fuhr.org>
Re: BUG #4618: nolock changes first column name of query result set to 'nolock' Tom Lane <tgl@sss.pgh.pa.us>
brian wrote: > The following bug has been logged online: > > Bug reference: 4618 > Logged by: brian > Email address: b4kramer@yahoo.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
В списке pgsql-bugs по дате отправления
От: brian
Дата:
От: Michael Fuhr
Дата: