On 11/14/2013 01:05 PM, Dinesh Kumar wrote:
> Hi,
>
> I believe this has been fixed on this
> commit 3dfa02a90bfa5202c305187cf90baea1b46f6240.
>
> Could you try it once, with the latest master branch.
>
Sorry for the late reply. A colleague confirms that that commit fixes
it so I guess my only su
(1) Why are you posting on the pgAdmin support list? Is the problem happening
inside pgAdmin?
(2) Just a wild guess… I've not seen this with Postgres, but with in past
experience with another database system we were getting NaNs caused by users
pasting text into our custom app. As I recall vagu
