SEO

#1 (**permalink**) 04-17-2008, 04:35 PM

> -----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/p...dmin3error.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.

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

#2 (**permalink**) 04-17-2008, 04:35 PM

Dave Page wrote:

>>
>>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.

I don't see errors on win32 or linux, but the code wasn't clean.
Actually, I thought the offending line was just a leftover from ancient
times, when we didn't have Write(.., bool). Now we *really* have those
methods.

Regards,
Andreas

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: Upgrade problem(Ver 1.3.0)