Re: Upgrade problem(Ver 1.3.0) - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Upgrade problem(Ver 1.3.0)
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E472BDC6@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Upgrade problem(Ver 1.3.0)  ("Hiroshi Saito" <saito@inetrt.skcapi.co.jp>)
Responses Re: Upgrade problem(Ver 1.3.0)  (Andreas Pflug <pgadmin@pse-consulting.de>)
List pgadmin-hackers

> -----Original Message-----
> From: Hiroshi Saito [mailto:saito@inetrt.skcapi.co.jp]
> Sent: 29 March 2005 14:27
> To: Andreas Pflug
> Cc: pgadmin-hackers@postgresql.org; Dave Page
> Subject: Upgrade problem(Ver 1.3.0)
>
> Hi Andreas.
>
> An error occurs when upgraded to 1.3.x from 1.2.x.
>
> 1.2.x
>     wxString val;
>     Read(wxT("Export/Unicode"), &val, wxT("No"));
>     exportUnicode = StrToBool(val);
> 1.3.x
>     Read(wxT("Export/Unicode"), &exportUnicode, false);
>
> It is written in registry, and it goes on on it.
> I think that you must take this treatment into consideration.
> See,
> http://cre-ent.skcapi.co.jp/~saito/pgadmin3/pgAdmin3error.jpg
>
> This phenomenon is unpleasant though it is only the beginning.:-(

Not just 1.2 to 1.3 - I noticed it after a cvs update of 1.3 last night.

Regards, Dave.

pgadmin-hackers by date:

Previous
From: "Dave Page"
Date:
Subject: V1.2.1 uploaded
Next
From: cvs@developer.pgadmin.org
Date:
Subject: CVS Commit by andreas: Fix reading/writing bool config values