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

Re: Upgrade problem(Ver 1.3.0)

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp>,"Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>
Cc: <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Upgrade problem(Ver 1.3.0)
Date: 2005-03-29 13:37:52
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E472BDC6@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-hackers
 

> -----Original Message-----
> From: Hiroshi Saito [mailto:saito(at)inetrt(dot)skcapi(dot)co(dot)jp] 
> Sent: 29 March 2005 14:27
> To: Andreas Pflug
> Cc: pgadmin-hackers(at)postgresql(dot)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.

Responses

pgadmin-hackers by date

Next:From: cvsDate: 2005-03-29 17:42:57
Subject: CVS Commit by andreas: Fix reading/writing bool config values
Previous:From: Dave PageDate: 2005-03-29 13:36:34
Subject: V1.2.1 uploaded

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