From: | "Chris Travers" <chris(at)travelamericas(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Bug and/or feature? Complex data types in tables... |
Date: | 2004-01-01 01:20:25 |
Message-ID: | 002501c3d006$92958700$5e44053d@winxp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
This concept of using complex types in tables actually does have one
legitimate use. When used with casts and functions, you could use it as a
"poor-man's datatype" development method.
Here is a hypothetical example. Imagine for a moment that there was no CIDR
datatype. I could create a datatype as a set of ints and then create
casting functions which I could use for display of the data. This would be
similar to C except that it could be done by people like myself whose C
coding skills are not up to the level where I or anyone else would want them
in the database backend ;-)
Best Wishes,
Chris Travers
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2004-01-01 01:41:56 | Re: measuring disk usage of records |
Previous Message | Bruce Momjian | 2004-01-01 01:01:15 | Re: website doc search is extremely SLOW |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2004-01-01 01:47:06 | Re: [JDBC] PL/Java issues |
Previous Message | Barry Lind | 2004-01-01 00:34:51 | Re: [HACKERS] PL/Java issues |