| From: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: get rid of SQL_ASCII? |
| Date: | 2013-09-05 17:29:30 |
| Message-ID: | 20130905172930.GD30496@aart.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 05, 2013 at 09:53:18AM -0700, Joshua D. Drake wrote:
>
> On 09/05/2013 09:42 AM, Josh Berkus wrote:
> >
> >Peter,
> >
> >>Other ideas? Are there legitimate uses for SQL_ASCII?
> >
> >Migrating from MySQL. We've had some projects where we couldn't fix
> >MySQL's non-enforcement text garbage, and had to use SQL_ASCII on the
> >receiving side. If it hadn't been available, the user would have given
> >up on Postgres.
>
> iconv?
>
Yes, you can use iconv but then you have to check that it generated
values that do not break your system including the application logic.
That can prove a major stumbling block to changing DBs.
Regards,
Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-09-05 17:29:35 | Re: Analysis on backend-private memory usage (and a patch) |
| Previous Message | ktm@rice.edu | 2013-09-05 17:26:52 | Re: get rid of SQL_ASCII? |