Skip site navigation (1) Skip section navigation (2)

Re: pgAdmin III truncates numeric values in

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Miha Radej" <miha(dot)radej(at)siix(dot)com>,<pgadmin-support(at)postgresql(dot)org>
Subject: Re: pgAdmin III truncates numeric values in
Date: 2003-08-28 15:37:45
Message-ID: 03AF4E498C591348A42FC93DEA9661B844B53C@mail.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-support

> -----Original Message-----
> From: Miha Radej [mailto:miha(dot)radej(at)siix(dot)com] 
> Sent: 28 August 2003 16:30
> To: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] pgAdmin III truncates numeric values in
> 
> 
> Hi!
> 
> I was wondering, if one double clicks on a field (truncated 
> or not) and 
> doesn't make any changes, then pgAdmin doesn't need to change 
> the data? If 
> I understand correctly, the value entered was 1.51515151515151512 and 
> displayed as 1.515152. If Masoud wouldn't have double clicked 
> on the field 
> then pgAdmin wouldn't change the value as it apparently did 
> in this case. So, does pgAdmin, whenever one double clicks on 
> a field and then somewhere 
> else, consider that data as altered and updates the table?

No, it only updated it because the data had changed. pgAdmin just didn't
realise that it was changed by wxWindows, not the user. Andreas
committed a fix for another bug that actually replaced this wx code
anyway, and appears to solve this problem as well.

Regards, Dave.

pgadmin-support by date

Next:From: Donald FraserDate: 2003-08-29 17:36:37
Subject: pgAdmin III No Trigger Functions available
Previous:From: Miha RadejDate: 2003-08-28 15:30:26
Subject: Re: pgAdmin III truncates numeric values in

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group