Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by hub.org (8.10.1/8.10.1) with ESMTP id e9FKQbR87988 for ; Sun, 15 Oct 2000 16:26:37 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e9FKQOB05473; Sun, 15 Oct 2000 16:26:24 -0400 (EDT) To: josh@agliodbs.com cc: sqllist Subject: Re: Variable-length Types In-reply-to: <39E9F80C.D9BE2054@agliodbs.com> References: <871yxi432t.fsf@matt.w80.math-hat.com> <39E9F80C.D9BE2054@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Sun, 15 Oct 2000 11:31:40 -0700" Date: Sun, 15 Oct 2000 16:26:24 -0400 Message-ID: <5470.971641584@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200010/133 X-Sequence-Number: 1795 Josh Berkus writes: > I'm a bit confused on custom type declarations, actually. I'd like to > create a custom type for American phone numbers, such that: > ... > 1. Can I reference a custom function (phoneformat) in a type definition? Of course. The input and output converters for the new type would be the natural place to do the reformatting. You'd probably make the input converter do error checking, insertion of default area code, and reduction to a pure digit string, and then make the output converter insert the fluff data like parentheses and dashes. However, building a new type for this seems like overkill, because you'd also have to supply a set of functions and operators for the type. It would be a lot less work just to provide a normalization function interpret_phone_no(text) returns text which could be invoked explicitly, eg insert into tab values (..., interpret_phone_no('5551212'), ...) or implicitly in ON INSERT and ON UPDATE triggers for the table. > 3. What sort of trouble am I going to get into trying to pull data from > a custom type into an external interface (i.e. PHP4)? Good question --- the interface code might or might not have a sensible default behavior for types it doesn't recognize. regards, tom lane