=?iso-8859-15?Q?Pierre-Fr=E9d=E9ric_Caillaud?= <[EMAIL PROTECTED]> writes:
> When I use UTF-8 encoding for my database. upper and lower() functions
> break (no longer process accented chars correctly).
This is fixed for 8.0.
regards, tom lane
-
When I use UTF-8 encoding for my database. upper and lower() functions
break (no longer process accented chars correctly). This is with the
correct encoding [EMAIL PROTECTED] I think, for CTYPES et al.
---(end of broadcast)---
TIP 9: the planne
On 8/6/2004 11:29 AM, Gordon Ross wrote:
Is it possible to make a column case insensitive, without having to pepper your
SELECTs with lots of lower() function calls (and forgetting to do it at times !)
(I'm on 7.4.3)
With a little bit of legwork you can create an itext data type. It would
just us
I create every time i need this, a copy of this field filled out by a
trigger
on insert and update that holds the upper (or lower for you) value of
the orginal field like this:
create table "users" (
"email" varchar(255),
...
"u_email" varchar(255)
...
);
CREATE OR REPLACE FUNCTION "public"."
On Fri, 2004-08-06 at 11:29, Gordon Ross wrote:
> Is it possible to make a column case insensitive, without having to pepper your
> SELECTs with lots of lower() function calls (and forgetting to do it at times !)
You could make yourself a set returning function to do this job -- but
that is proba
Is it possible to make a column case insensitive, without having to pepper your
SELECTs with lots of lower() function calls (and forgetting to do it at times !)
(I'm on 7.4.3)
Thanks,
GTG
Gordon Ross,
Network Manager/Rheolwr Rhydwaith
Countryside Council for Wales/Cyngor Cefn Gwlad Cymru
---
