Обсуждение: pg admin 92 beta 3 - bug report - row number 19 is out of range 0..18

Поиск
Список
Период
Сортировка

pg admin 92 beta 3 - bug report - row number 19 is out of range 0..18

От
"Gary Clarke (M4 Systems Ltd)"
Дата:

Hello to pgadmin dev team

(nice app by the way)

 

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

 

Regards

 

Gary

 

garyclarke@m4systems.com   ceo   www.m4systems.com   +44 7710 701 252

 

 

Description: Machine generated alternative text: ] postgres 92 b3 (192.168.221.28:5432) LIWÃIACL
Ó Databases (3) Notice
O.O Ipostgres
e CataLogs (2)
¡‘ Ø ANSI (information_schema) row number 19 is out of range 0.18
tho PostgreSQL (pg_cataLog)
fl Casts (9)
W’ Extensions (19) [ 0K ]
Foreign Data Wrappers (0) L ____________________________
I anatiapec 151 . r

 

Screen clipping taken: 18/08/2012 08:37

 

 

 

Re: pg admin 92 beta 3 - bug report - row number 19 is out of range 0..18

От
Guillaume Lelarge
Дата:
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