Thread: bug using sequences

Hi!
I've found a mistake using PGADMIN 1.6 or PGADMIN 1.8 beta5:
When I make a sequence with negative values, it works but PGADMIN is not 
able to show me the correct values.

This is an exemple:
PGADMIN shows me this:

CREATE SEQUENCE dsi.dsi_pha_molecule_id_seq INCREMENT 18446744073709551615 MINVALUE 18446744073709541616 MAXVALUE 0
START18446744073709549616 CACHE 1;
 
ALTER TABLE dsi.dsi_pha_molecule_id_seq OWNER TO postgres;

but in fact that sequence send me negative values...

Olivier Bouiron

-- 
Olivier Bouiron
Institut Sainte Catherine
AVIGNON

Tél: 04 90 27 57 43

Olivier Bouiron a écrit :
> I've found a mistake using PGADMIN 1.6 or PGADMIN 1.8 beta5:
> When I make a sequence with negative values, it works but PGADMIN is not
> able to show me the correct values.
> 
> This is an exemple:
> PGADMIN shows me this:
> 
> CREATE SEQUENCE dsi.dsi_pha_molecule_id_seq
>  INCREMENT 18446744073709551615
>  MINVALUE 18446744073709541616
>  MAXVALUE 0
>  START 18446744073709549616
>  CACHE 1;
> ALTER TABLE dsi.dsi_pha_molecule_id_seq OWNER TO postgres;
> 
> but in fact that sequence send me negative values...
> 

Well, they are declared wxULongLong, ie unsigned long. I wonder why. It
should be simple enough to change that to wxLongLong. I'll write a patch
for this.

Regards.


-- 
Guillaume.http://www.postgresqlfr.orghttp://dalibo.com

Guillaume Lelarge a écrit :
> Olivier Bouiron a écrit :
>> I've found a mistake using PGADMIN 1.6 or PGADMIN 1.8 beta5:
>> When I make a sequence with negative values, it works but PGADMIN is not
>> able to show me the correct values.
>>[...]
> 
> Well, they are declared wxULongLong, ie unsigned long. I wonder why. It
> should be simple enough to change that to wxLongLong. I'll write a patch
> for this.
> 

Done. Should be in RC1.

Regards.


-- 
Guillaume.http://www.postgresqlfr.orghttp://dalibo.com