From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
Cc: | hackers(at)postgreSQL(dot)org (PostgreSQL-development) |
Subject: | Re: [HACKERS] Data types |
Date: | 1998-04-09 06:35:12 |
Message-ID: | 199804090635.CAA05689@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> 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(at)candle(dot)pha(dot)pa(dot)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)
From | Date | Subject | |
---|---|---|---|
Next Message | David Gould | 1998-04-09 07:41:38 | Re: [HACKERS] On improving OO support in posgresql and relaxing oid bottleneck at the same time |
Previous Message | Thomas G. Lockhart | 1998-04-09 05:02:24 | Re: [HACKERS] Data types |