From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | "Gary Clarke (M4 Systems Ltd)" <garyclarke(at)m4systems(dot)com> |
Cc: | "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org>, "Misa Simic (M4 Systems Ltd)" <misasimic(at)m4systems(dot)com>, "Branka Stancic (M4 Systems Ltd)" <brankastancic(at)m4systems(dot)com> |
Subject: | Re: pg admin 92 beta 3 - bug report - row number 19 is out of range 0..18 |
Date: | 2012-08-26 07:59:06 |
Message-ID: | 1345967946.5678.2.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi,
On Sat, 2012-08-18 at 07:54 +0000, Gary Clarke (M4 Systems Ltd) wrote:
> Hello to pgadmin dev team
> (nice app by the way)
>
Thanks.
> I noticed this pgadmin bug in beta version 2 -
> is still present in beta version 4 released yesterday.
>
> Not critical but I thought would be worth advising you.
>
> when I try to - object browse - pg_catalog - in any database - I get error notice - row number 19 is out of range 0..18
>
> about 25 clicks required to get past error message - then browses ok
>
> pg admin 1.16 beta 4 - Running on 64 bit windows
>
> postgres v 9.2 beta 3 - running on Ubuntu 12.04 - on virtual box v1.18
>
> postgres build has been changed - increased max for object identifiers to 256 character
>
> NAMEDATALEN 64 to 256
>
Are you sure you were using pgAdmin 1.16 beta 4? Because I can't
reproduce your issue, even with a NAMEDATALEN to 256 on PostgreSQL 9.2
RC 1.
If you were using pgAdmin 1.16 beta 4, then I'll need more informations
to fix the bug.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Colin Beckingham | 2012-08-26 08:17:14 | Re: Font size control in edit data window |
Previous Message | Guillaume Lelarge | 2012-08-26 07:23:10 | Re: Font size control in edit data window |