MIME-Version: 1.0
References: 
 <CADHFRch1=ND1TpiOidJELBdJJSugn-H1d3vyjg9gh9Nw1dZCgg@mail.gmail.com>
 <CAKAnmmKhepxPzLWiU2JMNWsNiwLmQAyKCgV-f2dMot1hKVa-hA@mail.gmail.com>
 <CAJexoSK3grH+4khLYMDH=dBwbZxx=F-5GUM1rzHh5fzT_GGuwg@mail.gmail.com>
 <CADHFRcj_4uaxjNSJCCmB8LBE3w5BHh8a7u3pMpZiyDQSbawTyA@mail.gmail.com>
 <CAJexoSLZKvxVBoueN0_YjTkSu4-G1A1wFbPCqw_9S4b+cs9NXA@mail.gmail.com>
 <848536.1701750235@sss.pgh.pa.us>
In-Reply-To: <848536.1701750235@sss.pgh.pa.us>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Tue, 5 Dec 2023 15:54:08 -0500
Message-ID: 
 <CAKAnmmKbVmBpbHqBiYYYSp=bTPU4+1J0BnpjrjTMJrE=xvOg_A@mail.gmail.com>
Subject: Re: Overcoming Initcap Function limitations?
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Steve Midgley <science@misuse.org>, Bo Guo <bo.guo@gisticinc.com>,
	pgsql-sql <pgsql-sql@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000c1bd25060bc971ca"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKAnmmKbVmBpbHqBiYYYSp%3DbTPU4%2B1J0BnpjrjTMJrE%3DxvOg_A%40mail.gmail.com>
Precedence: bulk

--000000000000c1bd25060bc971ca
Content-Type: text/plain; charset="UTF-8"

I agree with Tom. Store the original: let the frontend uppercase themselves
if they want it that way. If they decide to force the transforms back down
to you, you won't have spoiled your input. If they are querying on that
column, a functional index on lower(col) would be nice. To answer your
original question, yes, let the front end deal with the problem, leaving
you time to worry about more traditional database-related problems. :)

Cheers,
Greg

--000000000000c1bd25060bc971ca
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I agree with Tom. Store the original: let the fronten=
d uppercase themselves if they want it that way. If they decide to force th=
e transforms back down to you, you won&#39;t have spoiled your input. If th=
ey are querying on that column, a functional index on lower(col) would be n=
ice. To answer your original question, yes, let the front end deal with the=
 problem, leaving you time to worry about more traditional database-related=
 problems. :)</div><div><br></div><div>Cheers,</div><div>Greg</div><div><br=
></div></div>

--000000000000c1bd25060bc971ca--