| From: | Aaron Koning <aaronkoning(at)gmail(dot)com> |
|---|---|
| To: | ketema(at)ketema(dot)net |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Best Data type for Binary Data? |
| Date: | 2006-01-05 22:08:36 |
| Message-ID: | 1319fbba0601051408x1c85b206x9510c71ea1ccf8d3@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
BYTEA is the easiest from my point of view. I like being able to treat my
binary data more like any other field (e.g. date, text, etc). Heres some
light reading on the BLOB/BYTEA debate:
http://search.postgresql.org/www.search?cs=utf-8&fm=on&st=20&dt=back&q=blob+bytea
Aaron
On 1/5/06, Ketema Harris <ketema(at)gmail(dot)com> wrote:
>
> Hi, I would like to store binary data from a tcpdump (libpcap) file in a
> table. What is the best type to use? i have read posts saying lo, oid, and
> bytea. Which one would be best for this scenario?
>
> Thanks, ketema
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2006-01-05 22:17:21 | Re: 'Official' definition of ACID compliance? |
| Previous Message | Richard_D_Levine | 2006-01-05 22:07:52 | Re: 'Official' definition of ACID compliance? |