From: manchicken <manchicken@notsosoft.net>
Organization: notsosoft.net
To: pgsql-sql@postgresql.org
Subject: Re: tsearch2() trigger and domain types...
Date: Tue, 19 Jun 2007 08:55:46 -0500
User-Agent: KMail/1.9.7
References: <200706181610.00270.manchicken@notsosoft.net>
	<10334.1182207590@sss.pgh.pa.us>
In-Reply-To: <10334.1182207590@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200706190855.47398.manchicken@notsosoft.net>

On Monday 18 June 2007 17:59:50 Tom Lane wrote:
> "Michael D. Stemle, Jr." <manchicken@notsosoft.net> writes:
> > For standardization in my database I use a domain (login_t) for my login
> > column in my profile table.
> >
> > Well, here's what I get upon every update and insert to the profile
> > table: WARNING:  TSearch: 'login' is not of character type
>
> The tsearch trigger seems to insist that the column be text, varchar(n),
> or char(n) ... no domains need apply :-(
>
> I'm not real sure why it doesn't just invoke the column's output
> function and be datatype-agnostic.  Or at least do that when the
> shortcut "I know what text looks like" path isn't applicable.

Is there any way to cast these column datatypes in the trigger to fool it, or 
is the only way to fix this to reconstruct the table without domains?  I'd 
really prefer not to abandon domains if at all possible.

-- 
~ manchicken <><
(A)bort, (R)etry, (I)nfluence with large hammer.
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0


Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html