On 09/01/2008, Hiroshi Saito <[EMAIL PROTECTED]> wrote:
> Hi Dave.
>
> Yeah, we know the user who had the same problem in the past. However, In
> Japan,
> it needed to be written by encoding of a client, and We did not want to set
> an initial
> value to UTF-8. Therefore, It is need recognized by
Hi Dave.
Yeah, we know the user who had the same problem in the past. However, In Japan,
it needed to be written by encoding of a client, and We did not want to set an initial
value to UTF-8. Therefore, It is need recognized by the warning message.
How is an attached patch proposal?
Regards,
On 08/01/2008, Andrew <[EMAIL PROTECTED]> wrote:
> Excellent,
>
> Thanks Hiroshi Saito, that worked a treat, I really appreciate you
> posting those images. Apologies for taking up your time for something I
> probably could have figured out by RTFM.
Yes, thanks Hiroshi (our resident encoding guru
Excellent,
Thanks Hiroshi Saito, that worked a treat, I really appreciate you
posting those images. Apologies for taking up your time for something I
probably could have figured out by RTFM.
However, IMHO I still think it is a defect, in that it shouldn't really
be saving a 0 byte file sile
Hi.
Please see,
http://winpg.jp/~saito/pgAdmin/QueryTool_check/
It is necessary to set reading and writing of an option to UTF-8.
Although ANSI and UTF-8 are possible as for reading, the option
is required for writing.
Regards,
Hiroshi Saito
- Original Message -
From: "Andrew" <[EMAIL
As the attachment did not appear to make it through, the actual SQL that
causes the 0 byte save is as follows:
DROP TABLE IF EXISTS bad_data;
CREATE TABLE bad_data (
id int NOT NULL,
bad_data varchar(50) NOT NULL,
PRIMARY KEY (id)
);
INSERT INTO bad_data (id, bad_data) VALUES
(1, 'Dhabīḥah
Hi Dave,
Ignore issue 2 then if it is a known issue.
With issue 1, I have isolated two offending characters that cause the
problem: "ī" (c4ab) and "ḥ" (e1b8a5). The inclusion of either one of
them will lead to an empty file being stored. I'm using the characters
for phonetic Arabic transliter
On 07/01/2008, Andrew <[EMAIL PROTECTED]> wrote:
> OS: WinXP SP2
> PC: Pentium D 3 GHz, 2 GB RAM
> pgAdmin ver: 1.8.0, 1.8.1
> postgresql ver: 8.2.5-1
>
> I haven't been able to find these issues on the Internet or on the
> pgAdmin web site, so hopefully they are not duplicates of existing.
>
> Iss
OS: WinXP SP2
PC: Pentium D 3 GHz, 2 GB RAM
pgAdmin ver: 1.8.0, 1.8.1
postgresql ver: 8.2.5-1
I haven't been able to find these issues on the Internet or on the
pgAdmin web site, so hopefully they are not duplicates of existing.
Issue 1:
Working on a ~ 1 MB *.sql file from the Query Tool - a
