| From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
|---|---|
| To: | Marcel van Pinxteren <marcel(dot)van(dot)pinxteren(at)gmail(dot)com> |
| Cc: | Jasen Betts <jasen(at)xnet(dot)co(dot)nz>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Case insensitive collation |
| Date: | 2013-01-18 18:30:59 |
| Message-ID: | CAFaPBrRVAK_AbgMr+GRf1MdSvhtw4LnkqhMGK_02B2kOWmQ31w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jan 18, 2013 at 6:13 AM, Marcel van Pinxteren <
marcel(dot)van(dot)pinxteren(at)gmail(dot)com> wrote:
> Desired behaviour:
> 1. If there is a row with 'ABC' (in a unique column) in the table, a row
> with 'abc' should not be allowed
> 2. If I do SELECT * FROM aTable WHERE aColumn = 'ABC', I should see a row
> with 'abc' as well (if there is one in the table)
>
> This has been described in this mailing list a few months ago, in more
> detail.
>
Have you seen the citext module?:
http://www.postgresql.org/docs/current/static/citext.html.
It does pretty much that (albeit by having columns be the citext type
instead of text or varchar).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2013-01-18 18:43:18 | Re: Temp table's effect on performance |
| Previous Message | Adrian Klaver | 2013-01-18 17:39:08 | Re: Understanding TIMESTAMP WITH TIME ZONE |