| From: | Malcontent null <malcontent(at)msgto(dot)com> |
|---|---|
| To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Why Not MySQL? |
| Date: | 2018-05-03 20:42:27 |
| Message-ID: | 31019427.957328947583.JavaMail.root@mua1.msgto.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The Hermit Hacker <scrappy(at)hub(dot)org> wrote:
>
>On Tue, 2 May 2000, Tim Uckun wrote:
>
>> If I can't get my questions answered about case sensitivity issues here
>> (no help so far) I will most likely to use it myself.
>
>What questions? *raised eyebrow*
>
>
The question dealt with trying to acieve case insensitive collation in postgres. Specifically about possibly rewriting the text_cmp or the varchareq functions. I am wondering what kind of mayhem that might cause. I was told by someone who tried it that it's possible to overload the ~~ (like) operator but that dropping the = operator cripples the database so that it's not possible to overload the = operator.
As to why I might want to do this I'll answer that one in response to another question :)
----------
Message To Spammers -- Game Over! Get spam-free email at http://www.MsgTo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Malcontent null | 2018-05-03 21:04:53 | Re: Why Not MySQL? |
| Previous Message | Tom Lane | 2018-05-03 20:11:25 | Re: unused_oids script is broken with bsd sed |