Robert Haas wrote:
> Tom Lane wrote:
>> There's a large undercurrent of "I say it's bad for you" in
>> this thread, with frankly nothing to back it up. If we try to
>> be as nanny-ish as you're suggesting here, we'll just annoy
>> users.
>
> +1.
+1
I can definitely see a place for an ASCII7 en
On Fri, Sep 6, 2013 at 10:19 AM, Tom Lane wrote:
> There's a large undercurrent of "I say it's bad for you" in this thread,
> with frankly nothing to back it up. If we try to be as nanny-ish as
> you're suggesting here, we'll just annoy users.
+1.
--
Robert Haas
EnterpriseDB: http://www.enterp
Craig Ringer writes:
> What we SHOULD be doing is making it an explicit decision to use
> SQL_ASCII, and NEVER creating a cluster or database with that encoding
> by default. Ever. If we can't decide what the correct default encoding
> is (say, if locale is "C") we should error out unless a specif
On 09/06/2013 09:14 AM, Craig Ringer wrote:
On 09/05/2013 08:47 PM, Peter Eisentraut wrote:
Other ideas? Are there legitimate uses for SQL_ASCII?
IMO people who want SQL_ASCII should actually be storing everything in
`bytea`; that's a truer reflection of what they're actually storing,
retriev
On 09/05/2013 08:47 PM, Peter Eisentraut wrote:
> Other ideas? Are there legitimate uses for SQL_ASCII?
IMO people who want SQL_ASCII should actually be storing everything in
`bytea`; that's a truer reflection of what they're actually storing,
retrieving, and working with and how they're doing it
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, t
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 g
On 09/05/2013 10:02 AM, Alvaro Herrera wrote:
> Joshua D. Drake wrote:
>> iconv?
>
> Command Prompt helped a customer normalize encodings in their data,
> which was a mixture of Latin1 and UTF8. PGLoader was used for this, in
> two stages; the first run in UTF8 saved the rejected data to a file
>
On Thu, Sep 05, 2013 at 09:42:17AM -0700, 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
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.
--
J
Joshua D. Drake wrote:
>
> On 09/05/2013 09:42 AM, Josh Berkus wrote:
> >>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.
On Thu, Sep 05, 2013 at 08:47:32AM -0400, Peter Eisentraut wrote:
> Can we consider getting rid of the SQL_ASCII server-side "encoding"? I
> don't see any good use for it, and it's often a support annoyance, and
> it leaves warts all over the code. This would presumably be a
> multi-release effor
On 05.09.2013 15:47, Peter Eisentraut wrote:
Can we consider getting rid of the SQL_ASCII server-side "encoding"? I
don't see any good use for it, and it's often a support annoyance, and
it leaves warts all over the code. This would presumably be a
multi-release effort.
I think "warts all ove
On Thu, Sep 5, 2013 at 7:47 AM, Peter Eisentraut wrote:
> Can we consider getting rid of the SQL_ASCII server-side "encoding"? I
> don't see any good use for it, and it's often a support annoyance, and
> it leaves warts all over the code. This would presumably be a
> multi-release effort.
>
> As
14 matches
Mail list logo
