Обсуждение: pgAdmin III v1.6 Beta 1 - Pg-8.2beta1: Grid editor problem

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

pgAdmin III v1.6 Beta 1 - Pg-8.2beta1: Grid editor problem

От
"Alexander Kirpa"
Дата:
During editing table within grid editor
receive next error:
2006-10-04 16:57:27 9261 ERROR:  type "pg_catalog.smallint" does not 
exist at character 103
2006-10-04 16:57:27 9261 STATEMENT:  UPDATE axxxxxxxxxxxx SET 
titlexxxxxxxxxxxx='Qxxxxxxxxxxxxxxxxx'::pg_catalog.text
WHERE axxx = '1047'::pg_catalog."smallint"
(axxx - int2) - similar problem should exist for integer and bigint, 
because in pg_catalog.pg_type exist only int2/4/8,
but psql in \d+ use smallint etc.
After replace smalint on int2 in 'Query tool' - no error

and
a) not useful removing (lost) definition 'int2/4/8'
from 'Data Types' in, for instance, 'New Column...'
b) Query tool - not useful policy in case big size of 'Output pane' 
after 'Restore' of window size from Maximize(full) windows size

Best regards,Alexander Kirpa



Re: pgAdmin III v1.6 Beta 1 - Pg-8.2beta1: Grid editor problem

От
"Dave Page"
Дата:

> -----Original Message-----
> From: Alexander Kirpa [mailto:postgres@bilteks.com]
> Sent: 04 October 2006 15:50
> To: pgadmin-support@postgresql.org
> Subject: pgAdmin III v1.6 Beta 1 - Pg-8.2beta1: Grid editor problem
>
> During editing table within grid editor
> receive next error:
> 2006-10-04 16:57:27 9261 ERROR:  type "pg_catalog.smallint" does not
> exist at character 103
> 2006-10-04 16:57:27 9261 STATEMENT:  UPDATE axxxxxxxxxxxx SET
> titlexxxxxxxxxxxx='Qxxxxxxxxxxxxxxxxx'::pg_catalog.text
> WHERE axxx = '1047'::pg_catalog."smallint"
> (axxx - int2) - similar problem should exist for integer and bigint,
> because in pg_catalog.pg_type exist only int2/4/8,
> but psql in \d+ use smallint etc.
> After replace smalint on int2 in 'Query tool' - no error

This has been fixed in beta 2.

> and
> a) not useful removing (lost) definition 'int2/4/8'
> from 'Data Types' in, for instance, 'New Column...'

pgAdmin now uses the spec compliant names for these types as PostgreSQL
does by default (integer, bigint etc).

> b) Query tool - not useful policy in case big size of 'Output pane'
> after 'Restore' of window size from Maximize(full) windows size

Sorry, I don't understand what you mean.

Regards Dave