| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: VARIANT / ANYTYPE datatype |
| Date: | 2011-05-10 21:57:20 |
| Message-ID: | BANLkTikEZsPZS4EM-fnLitm2m5eVWi6U1A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 4, 2011 at 5:58 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> A customer came to us with this request: a way to store "any" data in a
> column. We've gone back and forth trying to determine reasonable
> implementation restrictions, safety and useful semantics for them.
> I note that this has been requested in the past:
> http://archives.postgresql.org/pgsql-general/2004-02/msg01266.php
I think its a reasonably common use case.
Would it be possible to do this with a "typed" hstore? Seems easier to
add something there than it would be to add the VARIANT type as
discussed here.
> both Oracle and MS-SQL have it
Do they? What types are they called?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2011-05-10 22:02:26 | Infinity bsearch crash on Windows |
| Previous Message | Tom Lane | 2011-05-10 21:55:21 | Re: Why not install pgstattuple by default? |