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 silently, when you think it has successfully
saved your changes, and then when you go back to the file you find the
data you have worked on is lost. If it is in a mode not to support the
characters, then it should alert you that it cannot save those
characters. However, I will leave that for the development team to
decide if it is defective behaviour or behaviour by design.
Cheers,
Andy
Hiroshi Saito wrote:
> 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" <archa@pacific.net.au>
>
>
> 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'),
> (2, 'ذَبِيْحَة');
>
> Cheers,
>
> Andy
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
>