> I haven't gotten farther than this yet, but it seems like any solution
> has _got_ to take advantage of some of the existing type mechanisms so
> that we have access to input/output routines for the type support info.
> SQL doesn't naturally lend itself to full OO extensibility, but perhaps
> we can extend the backend to handle syntax like
>
> typename(characteristic, characteristic,...)
>
> where the characteristics have properties stored in the type/attribute
> system and the backend knows how to meld the type with the support type
> info (e.g. typeOutput = print("%s(%s)", typename, printTypeSupport) ).
>
> Does this ring a bell with anyone? Vadim?
How does atttypmod fit/not fit the need here? It is passed to all
input/output functions.
--
Bruce Momjian | 830 Blythe Avenue
maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)