Обсуждение: 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.:-(

regards,
Hiroshi Saito

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

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

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 29 March 2005 18:44
> To: Dave Page
> Cc: Hiroshi Saito; pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] Upgrade problem(Ver 1.3.0)
>
> 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.

I only saw them once (on XP), so I assumed it was a new (but missing)
regkey that was written when I exited. I had meant to email you about it
but got sidetracked.

Thanks anyway!

Regards, Dave.

Hi Andreas.

I appreciate your quick correspondence. But, it seems that it made
a new problem occur. I must confirm it again. However, I face a bed.
Again, tomorrow.
Thank you.

regards,
Hiroshi Saito

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

I only saw them once (on XP), so I assumed it was a new (but missing)
regkey that was written when I exited. I had meant to email you about it
but got sidetracked.

Thanks anyway!

Regards, Dave.