From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Case sensitivity |
Date: | 2013-12-11 15:16:25 |
Message-ID: | CALSLE1O_h_i6+9K3fHw2OtoQrxNFXPPysb6ksH_0_grRo0iAfg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general pgsql-hackers |
Can case-insensitive collation help here?
On Wed, Dec 11, 2013 at 4:55 PM, Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> wrote:
> Thanks John.
>
> Yes CITEXT would work, the only thing its needs DDL changes across and
> hence was looking for any such global database parameter setting while
> creating database. I have been looking at other discussions and doesn't
> look like anything of that coming up soon that makes database case
> insensitive.
>
> regards...
>
>
> On Wed, Dec 11, 2013 at 12:10 PM, John R Pierce <pierce(at)hogranch(dot)com>wrote:
>
>> On 12/10/2013 10:31 PM, Dev Kumkar wrote:
>>
>>> I know about CITEXT data type, but what am looking for is if there any
>>> parameter at database level which just makes the database case insensitive.
>>>
>>
>> there's nothing that will do that in postgres.
>>
>> whats wrong with using CITEXT ?
>>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2013-12-11 15:28:21 | Re: Case sensitivity |
Previous Message | Dev Kumkar | 2013-12-11 15:00:55 | Re: Scheduled Events |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2013-12-11 15:28:21 | Re: Case sensitivity |
Previous Message | Dev Kumkar | 2013-12-11 15:00:55 | Re: Scheduled Events |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2013-12-11 15:16:50 | Re: ANALYZE sampling is too good |
Previous Message | ktm@rice.edu | 2013-12-11 15:14:17 | Re: In-Memory Columnar Store |