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

2009-01-16 Thread Tom Lane
Michael Fuhr writes: > On Fri, Jan 16, 2009 at 01:22:48PM +0100, Magnus Hagander wrote: >> 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. > "with (nolock)" is a SQL Server-ism

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

2009-01-16 Thread Michael Fuhr
On Fri, Jan 16, 2009 at 01:22:48PM +0100, Magnus Hagander wrote: > brian wrote: > > 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

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

2009-01-16 Thread Magnus Hagander
brian wrote: > The following bug has been logged online: > > Bug reference: 4618 > Logged by: brian > Email address: b4kra...@yahoo.com > PostgreSQL version: 8.3.5 build1400 > Operating system: windows xp > Description:nolock changes first column name of query result s

[BUGS] BUG #4618: nolock changes first column name of query result set to 'nolock'

2009-01-16 Thread brian
The following bug has been logged online: Bug reference: 4618 Logged by: brian Email address: b4kra...@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: q