| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "Saraswat, Dhruv" <dhruv(dot)saraswat(at)thermofisher(dot)com>, "pgsql-sql(at)lists(dot)postgresql(dot)org" <pgsql-sql(at)lists(dot)postgresql(dot)org>, "Perumalla, Vijaya S(dot)" <Vijaya(dot)Perumalla(at)thermofisher(dot)com>, "AR, KarthikRaja" <karthikraja(dot)ar(at)thermofisher(dot)com>, "bhorhari, vikas" <vikas(dot)bhorhari(at)thermofisher(dot)com>, "SV, Sushanth" <sushanth(dot)sv(at)thermofisher(dot)com>, "Dahiya, Rohit" <rohit(dot)dahiya(at)thermofisher(dot)com>, "Thota, DurgaKumari" <Durga(dot)Kumari(at)thermofisher(dot)com>, "Venkatachalam, Sundarrajan" <Sundarrajan(dot)Venkatachalam(at)thermofisher(dot)com>, "Appandarajan, Vinoth" <vinoth(dot)a(at)thermofisher(dot)com>, "Barchhiha, Vaibhav" <vaibhav(dot)barchhiha(at)thermofisher(dot)com>, "Prajapati, Priya" <priya(dot)prajapati(at)thermofisher(dot)com>, "Kumar, Ravi" <ravi(dot)kumar(at)thermofisher(dot)com>, "Sarkar, Madhurima" <madhurima(dot)sarkar(at)thermofisher(dot)com> |
| Subject: | Re: UPPER() Function Not Working as Expected in PostgreSQL 12.5 Version |
| Date: | 2021-07-08 16:49:45 |
| Message-ID: | 1975904.1625762985@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Thu, Jul 8, 2021 at 2:26 AM Saraswat, Dhruv <
> dhruv(dot)saraswat(at)thermofisher(dot)com> wrote:
>> We have a table in which 1 of the columns is called ‘name’ with a datatype
>> of ‘name’. This column stores username values, for example ==>
>> dhruv(dot)saraswat(at)thermofisher(dot)com
> I unfortunately don't know the answer to your primary query but you are
> definitely misusing the "name" datatype.
Indeed. I suspect that this was done as some sort of substitute for
declaring the column with collation "C", and the reason it's acting
differently in v12 is related to the fact that name columns are no
longer forced to behave as though they have collation "C". We don't
have enough details to be sure of that though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Prajakta Chinchole | 2021-07-09 05:53:46 | Support for PostgreSQL stored procedure through ITX. |
| Previous Message | David G. Johnston | 2021-07-08 16:10:24 | Re: UPPER() Function Not Working as Expected in PostgreSQL 12.5 Version |