Re: CAST function for user defined type

From: Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: CAST function for user defined type
Date: 2007-01-22 16:49:46
Message-ID: 20070122164946.GB19861@yellowbank.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jan 22, 2007 at 11:40:08AM -0500, Tom Lane wrote:
> Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com> writes:
> > That cleared one hurdle, but I'm still not there yet.
>
> > % select 'fe43d07c0c624786bebfcb3357a2a13a'::y_octet_16;
> > y_octet_16
> > ----------------------------------
> > fe43d07c0c624786bebfcb3357a2a13a
>
> That's not invoking any cast function, but the type's typinput function
> (applied to a C-string).
>
> > When things are connected up this way,
> > what should the cast function expect to see as input?
>
> > % select encode( y_uuid_generate(), 'hex' )::y_octet_16;
> > ERROR: input string contains invalid characters
>
> If it's a cast from TEXT, it'll get the internal form of a TEXT datum,
> ie, a counted (and not null-terminated) string. You might look at
> textin() and textout() to grok the difference.

Got it working now. Thanks.

--
Ron Peterson
https://www.yellowbank.com/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Murphy 2007-01-22 17:00:20 selecting random rows
Previous Message Erik Jones 2007-01-22 16:44:08 Tracking database activity