| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Steve Midgley <science(at)misuse(dot)org>, Bo Guo <bo(dot)guo(at)gisticinc(dot)com>, pgsql-sql <pgsql-sql(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Overcoming Initcap Function limitations? |
| Date: | 2023-12-05 20:54:08 |
| Message-ID: | CAKAnmmKbVmBpbHqBiYYYSp=bTPU4+1J0BnpjrjTMJrE=xvOg_A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | intmail01 | 2023-12-19 08:26:46 | Wich program generates "list index out of range" ? pgadmin or the server ? |
| Previous Message | Tom Lane | 2023-12-05 04:23:55 | Re: Overcoming Initcap Function limitations? |