From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Andreas Peer <andipeer(at)gmx(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4421: convert_to() should be immutable |
Date: | 2008-09-18 10:57:38 |
Message-ID: | 48D23422.4060109@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Andreas Peer wrote:
> Well, the use case is a strange one... I would like to use a varchar()
> column for storing a variable-length vector of integers. The numbers are
> represented by the codepoints. Therefore, I need to sort them as binary
> data, not as characters. I would often need to get all the vectors that
> lie in between to vectors, therefore I need the "binary" index.
> And the code should be as database independent as possible, therefore I
> cannot use an array or another data type that may not be supported by
> other DBMS.
What makes you think messing around with encoding conversions is going
to be portable. Arrays are at least in the SQL standard.
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2008-09-18 11:02:15 | Re: [HACKERS] 0x1A in control file on Windows |
Previous Message | Abdul Rehman | 2008-09-18 07:44:19 | BUG #4423: Impementing replication via pgadmin |