Laurent ROCHE wrote:
> Hi,
>
> A bug has been introduced in the version 1.6.2: when backing up in a file,
> the file produced is not in UTF-8 format even though it is specified in the
> preferences.
>
> That used to work in 1.6.1
The UTF-8 option only applies to saved queries etc. not to backu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
Mike G a écrit :
> Hi,
>
> I downloaded 1.6.2 today, unzipped it, and then ran the upgrade.bat file
> since I had
> 1.6.1 installed.
>
> After rebooting the initial graphic that displays when opening pgadmin (same
> as the
> help->about graph
Hi,
I downloaded 1.6.2 today, unzipped it, and then ran the upgrade.bat file since
I had
1.6.1 installed.
After rebooting the initial graphic that displays when opening pgadmin (same as
the
help->about graphic), still displays the version as 1.6.1
1.6.1 was installed as part of the postgresq
Hi,
A bug has been introduced in the version 1.6.2: when backing up in a file, the
file produced is not in UTF-8 format even though it is specified in the
preferences.
That used to work in 1.6.1
Cheers,
[EMAIL PROTECTED]
The Computing Froggy
Hi All (and Guillaume),
Happy new year to all ... with less crazy bugs for everyone than in 2006 (and
that's including me ... please).
So I have upgraded to the latest and shiny PGAdmin 1.6.2 ... and I still have
the same problem I had in 1.6.1.
If I have a database set with UTF-8 character
I prefer '...' to be honest.
Personally I prefer a mix of the two suggestions " ..." (space then
three dots) lol but that's just me :)
--
Andy Shellam
NetServe Support Team
the Mail Network
"an alternative in a standardised world"
---(end of broadcast)
Erwin Brandstetter wrote:
> Hi developers! Hi Dave!
>
> Testing pgAdmin III v1.6.2 rev: 5837, client Win XP. Host Debian Sarge,
> PG 8.1.4.
>
> While having a look at the new release, I think I found an issue with
> truncated column comments. It seemed quite random at first, I guess I
> have figu
Milen A. Radev wrote:
> I just installed 1.6.2 (winxp) and noticed that the SQL Query window's
> title is empty.
>
> I can't remember what was the window's title in 1.6.1, but the fact
> that I noticed the missing title now probably means it's a new in
> 1.6.2. Is it on purpose?
>
Fixed, thanks.