Re: text column constraint, newbie question

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: RebeccaJ <rebeccaj(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: text column constraint, newbie question
Date: 2009-03-23 22:31:44
Message-ID: dcc563d10903231531h1872429dr1e02bb90579ecf73@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Mar 23, 2009 at 3:11 PM, RebeccaJ <rebeccaj(at)gmail(dot)com> wrote:
> Scott, your comment above introduced some new concepts to me, and now
> I'm thinking about foreign language text and other ways to be more
> flexible. I found this page that talks about encoding:
> http://www.postgresql.org/docs/8.3/static/multibyte.html
> And I wonder why you like SQL_ASCII better than UTF8, and whether
> others have any opinions about those two. (My web server's LC_CTYPE is
> C, so I can use any character set.) Wouldn't UTF8 allow more
> characters than SQL_ASCII?

No, SQL_ASCII will allow anything you wanna put into the database to
go in, with no checking. UTF8 will require properly formed and valud
UTF characters. Which is better depends a lot on what you're doing.
Note that SQL_ASCII is not 8 bit ASCII, it's a name for "anything
goes" instead. (Now Cole Porter is running through my head.. :) )

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Leif B. Kristensen 2009-03-23 22:43:48 Re: PostgreSQL versus MySQL for GPS Data
Previous Message Scott Marlowe 2009-03-23 22:28:20 Re: unexpected check constraint violation