| From: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: How to check if a field exists in NEW in trigger |
| Date: | 2019-08-09 18:30:20 |
| Message-ID: | 20190809183020.GB14917@hjp.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2019-08-07 15:54:33 -0700, Igal @ Lucee.org wrote:
> There is no reason, however, for an email address to be not-lower-cased, so
> while in some cases (no pun intended) it makes sense to keep the original
> CaSe while performing a case insensitive comparison, when it comes to email
> addresses I rather collapse the value upon insertion/update.
You should be aware that according to the specs, the local part of an
email address is case-sensitive. So JoeSmith(at)example(dot)com and
JoESmith(at)example(dot)com might be two distinct email addresses.
Admittedly I've never seen that in practice (although I've seen a lot of
other problems caused by people who made unwarranted assumptions about
email addresses).
hp
--
_ | Peter J. Holzer | we build much bigger, better disasters now
|_|_) | | because we have much more sophisticated
| | | hjp(at)hjp(dot)at | management tools.
__/ | http://www.hjp.at/ | -- Ross Anderson <https://www.edge.org/>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Souvik Bhattacherjee | 2019-08-09 22:06:10 | Bulk Inserts |
| Previous Message | Harold Falkmeyer | 2019-08-09 17:57:07 | Re: PostgreSQL 8.4 Tablespace Inconsistency |