From: | Joe Conway <joseph(dot)conway(at)home(dot)com> |
---|---|
To: | Ezra Epstein <akee(at)speakeasy(dot)net> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Oracle -> PostgreSQL ==> RAW -> ??? |
Date: | 2001-11-21 17:12:13 |
Message-ID: | 3BFBE06D.3010103@home.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Ezra Epstein wrote:
> Hi,
>
> I'm moving a database from Oracle to PostgreSQL. I use RAW (as in
> BINARY, as in BYTE(x) where x < 20) for quite a few columns that
> hold application generated keys, etc.
>
> How do I represent a RAW in PostgreSQL. I'm too much of a newbie to
> know how to create my own type. BIT seems to be wrong. And BYTEA
> can't be it either as there are all sorts of restrictions on using
> BYTEAs for keys. Seems OIDs are for BLOBs and this are not large
> binary objects...
>
> HELP!!! Answers, pointers, tips, doc refs, anything.
Most of the BYTEA restrictions are gone in 7.2 (about to go into 3rd
beta release). Specifically, you can now create btree indexes on BYTEA
columns. There's documentation too, in CVS and starting with beta3. Look
for "Binary Strings" under the section on datatypes and functions.
Hope this helps,
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-11-21 21:25:08 | Re: Documentation gap: Perl interfaces |
Previous Message | Joe Conway | 2001-11-21 17:04:41 | Re: [PATCHES] PQescapeBytea documentation patch |