From: | "Kevin Crenshaw" <kcrenshaw(at)viscient(dot)com> |
---|---|
To: | <ketema(at)ketema(dot)net>, <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Best Type to use |
Date: | 2006-01-05 20:10:04 |
Message-ID: | 20060105201007.2340D9DC812@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
You can also use the TEXT data type. Just convert your binary data to
base64 and write it to a field in your database like you would any other
type of text. This method takes up more space than the other methods but it
avoids some of the headaches of dealing with bytea.
CREATE OR REPLACE FUNCTION SAVE_TCP_DUMP(TEXT) RETURNS VOID AS $$
BEGIN
INSERT INTO mytable(tcpdump) VALUES($1);
END;
$$ LANGUAGE 'plpgsql';
HTH,
Kevin
_____
From: pgsql-novice-owner(at)postgresql(dot)org
[mailto:pgsql-novice-owner(at)postgresql(dot)org] On Behalf Of Ketema Harris
Sent: Thursday, January 05, 2006 2:19 PM
To: pgsql-novice(at)postgresql(dot)org
Subject: [NOVICE] Best Type to use
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? Depending on the type
can a sample insert and select statement be given as well?
Thanks,
ketema
From | Date | Subject | |
---|---|---|---|
Next Message | me | 2006-01-05 20:18:31 | index over boolean fields? |
Previous Message | Ketema Harris | 2006-01-05 19:18:57 | Best Type to use |