| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | pczulak(at)cybercom(dot)net, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Bug #705: Invalid UNICODE character sequence found |
| Date: | 2002-07-10 03:05:31 |
| Message-ID: | 20020710.120531.57461832.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> Short Description
> Invalid UNICODE character sequence found (0xc236)
Are you sure that above error message is for the below example?
I got: Invalid UNICODE character sequence found (0xc033)
> INSERT INTO ftp_log_t (ftp_log_source, ftp_from_site_id, ftp_file_status, ftp_file, ftp_log_date, ftp_file_date, ftp_file_size, ftp_insert_date) VALUES ('DD',300319,'ST','c:\Inetpub\FTPRoot\300319\300319TLOG07042002.zip','07-04-2002 14:30:36','2002-07-04 14:00',43514,'2002-07-05 08:22:43')
I don't know what data you actually want to store, but
for PostgreSQL \3003 means "octal 300 + ascii '3'" == 0xc033, which is
apparently wrong UTF-8 sequence. So PostgreSQL behaves as expected.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-07-10 03:08:07 | Re: Bug #706: Wrong shlib flag for GCC compilation on Solaris |
| Previous Message | pgsql-bugs | 2002-07-09 23:46:46 | Bug #706: Wrong shlib flag for GCC compilation on Solaris |