Re: BUG #4586: Supporting of Binary instead Bytea for Primary Keys

And how to specify that bytea MUST be exact 16 bytes? What about the speed
because this is very important?
1st of all when the length is variable then the speed is low.
2nd when the column is with bigger length which require pointer to the data
instead data, then the speed will be extremely low.

Miro.

On Wed, Dec 17, 2008 at 11:19 AM, Heikki Linnakangas <
heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:

> (please keep the mailing list cc'd. (or take this to a more relevant list,
> actually)).
>
> Miroslav Nachev wrote:
>
>> Thank you very much. How can I map PostgreSQL UUID to JPA Hibernate with
>> annotations? Serializable or BigInteger or byte[] or java.util.UUID?
>>
>
> No idea.
>
> The big disadvantage of bytea is that it is not possible to use that type
>> in
>> indexes and primary keys. Probably this restriction is because is very
>> slow
>> column type because instead to keep the data this column keeps pointer to
>> the data.
>>
>
> Huh? Of course it's possible:
>
> postgres=# CREATE TABLE foo (id bytea PRIMARY KEY);
> NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "foo_pkey"
> for table "foo"
> CREATE TABLE
> postgres=# CREATE INDEX i_foo ON foo (id);
> CREATE INDEX
> postgres=#
>
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
>