Skip site navigation (1) Skip section navigation (2)

Re: BUG #5268: PQgetvalue incorrectly returns 0 (corrected)

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5268: PQgetvalue incorrectly returns 0 (corrected)
Date: 2010-01-08 04:47:26
Message-ID: 4B46B8DE.9010403@catalyst.net.nz (view raw or flat)
Thread:
Lists: pgsql-bugs
(I forgot to cc -bugs...)

Mike Landis wrote:
>
> Two things strike me as odd about that...
> 1) What's the logic behind the owner of a table not automatically 
> getting a readonly privilege like SELECT?

Owner always has select on a table they have created.

> 2) I think it would be more logical to refuse to return a NULL result 
> from PQexec() than to return a result with the proper number of tuples 
> and columns, but inaccurate contents.

COUNT always returns a number (never null). Recall you are select from
the information schema table.

>
> It's also strange that Linux and Vista would produce different answers.

I suspect they do not. Its all in the permissions.

Cheers

Mark


pgsql-bugs by date

Next:From: Mark KirkwoodDate: 2010-01-08 05:51:19
Subject: Re: BUG #5268: PQgetvalue incorrectly returns 0
Previous:From: Michael FeltDate: 2010-01-08 04:02:39
Subject: Re: email addresses

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group