On Tuesday 19 June 2007 09:08:23 Tom Lane wrote:
> oidtype = getBaseType(oidtype);
I patched this in a FreeBSD 6.2 port. Attached is the patch. Thanks a lot
for the help on this. It works like a charm.
--
~ manchicken <><
(A)bort, (R)etry, (I)nfluence with large hammer.
09 F9 11 02 9D 74 E3
manchicken <[EMAIL PROTECTED]> writes:
> Is there any way to cast these column datatypes in the trigger to fool it,
No, you'd have to modify the trigger source code. It'd be a pretty
trivial change to allow domains over textual types:
continue;
}
On Monday 18 June 2007 17:59:50 Tom Lane wrote:
> "Michael D. Stemle, Jr." <[EMAIL PROTECTED]> 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:
"Michael D. Stemle, Jr." <[EMAIL PROTECTED]> 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 tse
Okay, so I have an interesting problem that I'm having a hard time figuring
out.
For standardization in my database I use a domain (login_t) for my login
column in my profile table. I'm trying to use the tsearch2() trigger to
index several columns, including the login column, into a column
ca
