| From: | Adrian von Bidder <avbidder(at)fortytwo(dot)ch> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: Best way to store case-insensitive data? | 
| Date: | 2010-06-11 06:48:42 | 
| Message-ID: | 201006110848.42952@fortytwo.ch | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
Heyho!
On Thursday 10 June 2010 22.50:23 Mike Christensen wrote:
> 2) Every time the user updates or saves their email, store it in
> lowercase, and every time I lookup an email, pass in a lowercase
> email.
I'd do it this way.  Plus either a CHECK condition on the table (email = 
lowercase(email)) (this will reliably catch all cases, but you will 
experience failures until you have found all cases)
Or a BEFORE trigger that converts email to lowercase.  (This is mostly 
transparent for storing, but I usually try to avoid triggers that modify 
data like this.  But that's probably just me.)
In either case, obviously you'll still need to change the code that is used 
for retrieving and comparing email addresses.
cheers
-- vbi
-- 
featured link: http://www.pool.ntp.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Christensen | 2010-06-11 07:01:18 | Re: Best way to store case-insensitive data? | 
| Previous Message | Adrian von Bidder | 2010-06-11 06:43:53 | Re: database response slows while pg_dump is running (8.4.2) |