Thread: pgAdmin III truncates numeric values in edit mode

pgAdmin III truncates numeric values in edit mode

From
Masoud Taherkhani
Date:
Hi:
 
1- I created the following table in pgAdmin III :
 
CREATE TABLE public.test (

exchng_rt numeric);

2- Then inserted a record in the table using

INSERT INTO test VALUES (1.5151515151515151515151515152);

3- SELECT * FROM test; returned correct data.

4- Then I right clicked on test table and selected View Data.

5- I double clicked on exchng_rt field but didn't make any changes. It changed the value to 1.515152

6- SELECT * FROM test; returned 1.515152

FYI, I am using Windows 2000 Professional, pgAdmin III Version 0.9.0 BETA 1 (Aug 6 2003) English version.

Thanks,

Masoud Taherkhani



Post your free ad now! Yahoo! Canada Personals

Re: pgAdmin III truncates numeric values in edit mode

From
"Dave Page"
Date:
Hi,
 
I can repeat this problem, and having looked into it, I think it's a wxWindows bug. I'll add it to the bugs list.
 
Thanks for the report.
 
Regards, Dave.
-----Original Message-----
From: Masoud Taherkhani [mailto:mtaherkhani@yahoo.com]
Sent: 27 August 2003 15:25
To: pgadmin-support@postgresql.org
Subject: [pgadmin-support] pgAdmin III truncates numeric values in edit mode

Hi:
 
1- I created the following table in pgAdmin III :
 
CREATE TABLE public.test (

exchng_rt numeric);

2- Then inserted a record in the table using

INSERT INTO test VALUES (1.5151515151515151515151515152);

3- SELECT * FROM test; returned correct data.

4- Then I right clicked on test table and selected View Data.

5- I double clicked on exchng_rt field but didn't make any changes. It changed the value to 1.515152

6- SELECT * FROM test; returned 1.515152

FYI, I am using Windows 2000 Professional, pgAdmin III Version 0.9.0 BETA 1 (Aug 6 2003) English version.

Thanks,

Masoud Taherkhani



Post your free ad now! Yahoo! Canada Personals

Re: pgAdmin III truncates numeric values in edit mode

From
"Dave Page"
Date:
OK, no sooner did I commit that, than Andreas appears to have fixed it whilst fixing another issue!!
 
Regards, Dave.
-----Original Message-----
From: Dave Page
Sent: 28 August 2003 15:59
To: Masoud Taherkhani; pgadmin-support@postgresql.org
Subject: Re: [pgadmin-support] pgAdmin III truncates numeric values in edit mode

Hi,
 
I can repeat this problem, and having looked into it, I think it's a wxWindows bug. I'll add it to the bugs list.
 
Thanks for the report.
 
Regards, Dave.
-----Original Message-----
From: Masoud Taherkhani [mailto:mtaherkhani@yahoo.com]
Sent: 27 August 2003 15:25
To: pgadmin-support@postgresql.org
Subject: [pgadmin-support] pgAdmin III truncates numeric values in edit mode

Hi:
 
1- I created the following table in pgAdmin III :
 
CREATE TABLE public.test (

exchng_rt numeric);

2- Then inserted a record in the table using

INSERT INTO test VALUES (1.5151515151515151515151515152);

3- SELECT * FROM test; returned correct data.

4- Then I right clicked on test table and selected View Data.

5- I double clicked on exchng_rt field but didn't make any changes. It changed the value to 1.515152

6- SELECT * FROM test; returned 1.515152

FYI, I am using Windows 2000 Professional, pgAdmin III Version 0.9.0 BETA 1 (Aug 6 2003) English version.

Thanks,

Masoud Taherkhani



Post your free ad now! Yahoo! Canada Personals

Re: pgAdmin III truncates numeric values in edit

From
Andreas Pflug
Date:
Dave Page wrote:

> Hi,
>  
> I can repeat this problem, and having looked into it, I think it's a 
> wxWindows bug. I'll add it to the bugs list.
>  


Fixed.

When no numeric precision is specified, wxWindows will use its default 
of 6, which we don't like in this case.
I rewrote this code, eliminating another old bug at the same time.

Regards,
Andreas



Re: pgAdmin III truncates numeric values in edit mode

From
"Dave Page"
Date:

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 28 August 2003 16:10
> To: Dave Page
> Cc: Masoud Taherkhani; pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] pgAdmin III truncates numeric
> values in edit mode
>
>
> Dave Page wrote:
>
> > Hi,
> >
> > I can repeat this problem, and having looked into it, I think it's a
> > wxWindows bug. I'll add it to the bugs list.
> >
>
>
> Fixed.
>
> When no numeric precision is specified, wxWindows will use
> its default
> of 6, which we don't like in this case.
> I rewrote this code, eliminating another old bug at the same time.

Just noticed - thanks!! 1 problem now though, the horizontal scrollbar
eclipses the field unless you resize the row first. Do we need the
scrollbars - will keyboard navigation be enough?

Regards, Dave.