From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steve Midgley <science@misuse.org>
cc: Bo Guo <bo.guo@gisticinc.com>, Greg Sabino Mullane <htamfids@gmail.com>,
        pgsql-sql <pgsql-sql@lists.postgresql.org>
Subject: Re: Overcoming Initcap Function limitations?
In-reply-to: 
 <CAJexoSLZKvxVBoueN0_YjTkSu4-G1A1wFbPCqw_9S4b+cs9NXA@mail.gmail.com>
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>
Comments: In-reply-to Steve Midgley <science@misuse.org>
	message dated "Mon, 04 Dec 2023 20:12:34 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <848535.1701750235.1@sss.pgh.pa.us>
Date: Mon, 04 Dec 2023 23:23:55 -0500
Message-ID: <848536.1701750235@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/848536.1701750235%40sss.pgh.pa.us>
Precedence: bulk

Steve Midgley <science@misuse.org> writes:
> On Mon, Dec 4, 2023, 5:39 PM Bo Guo <bo.guo@gisticinc.com> wrote:
>> Your suggestions open up new potentials for me to explore.  At this
>> moment, I lean towards normalizing the database column values in upper
>> case, thereby out-sourcing the case-changing responsibility to the front
>> end.  I would love to hear from your thoughts on this pattern.

> It really depends on the use case. If your users are happy with all
> uppercase, that seems like a great solution: fast, cheap, and reliable!

FWIW, as an old database geek I'd lean more towards "store the original
input data".  If you are expecting the client-side display code to
transform the casing anyway, I don't see any advantage in smashing to
upper case beforehand.  And keeping the original casing could have
value down the road, if only for forensic purposes.

			regards, tom lane