Re: uppercase = lowercase - Mailing list pgsql-admin

For any of you out there that have tried this module already please forgive
me but there is a bug in the SQL install script.
While I have tried and tested the code under a public schema, when I
packaged up the install script I thought it would be tidier if it was all
put into the pg_catalog schema (due to the large amount of overloaded
functions). A simple append of pg_catalog in most cases worked but I
overlooked the correct format for the CREATE OPERATOR statement within
schemas (it was actually a cut and paste from pgAdmin II which gives the
incorrect format - poor excuse I know!).
While the original SQL script runs without any errors, and appears to work,
it may have some undesirable side effects. I therefore suggest you use the
updated attached install script (citext.sql - the other files remain
unchanged).
Regards
Donald Fraser.

Ps. I don't mind adding and maintaining the code under gborg, I just need
some guidance on how to do it... anyone done this before?

Tip: If you want to un-install the module, having already run the citext.sql
script file, simply execute the following SQL:
DROP FUNCTION citextin(cstring) CASCADE;
This will remove anything to do with the citext data type.

----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Robert Treat" <xzilla@users.sourceforge.net>
Cc: "Donald Fraser" <demolish@cwgsy.net>; "[ADMIN]"
<pgsql-admin@postgresql.org>
Sent: Wednesday, February 19, 2003 7:51 AM
Subject: Re: [ADMIN] uppercase = lowercase


> Robert Treat <xzilla@users.sourceforge.net> writes:
> > We get this question a lot, usually from folks converting from mysql.
> > Do any of the core folks think this is worth adding to contrib? Or
> > perhaps a project on gborg would be more appropriate?
>
> In the long run, the correct SQL-spec-compliant solution is selectable
> collation for each column, and then you could specify a case-insensitive
> collation for the columns you want to act this way.  But I don't really
> foresee that happening in the near future :-(.  In the meantime, a
> specialized datatype seems like an okay hack.
>
> I'd not favor putting it into the core distribution, because that would
> amount to a commitment to support it indefinitely, which I don't want
> to make.  contrib would be iffy for the same reason --- contrib tends
> to have a subtext of "this might be mainstream someday, if it gets
> polished up".  gborg, no problem.
>
> But that's just my $0.02.  Comments anyone?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>