[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] large object minimum storage
From:       Dustin Sallings <dustin () spy ! net>
Date:       1999-06-27 3:11:45
[Download RAW message or body]

On Sat, 26 Jun 1999, Kenneth Been wrote:

# I've pretty much decided to use arrays instead of blobs, and put the
# "overflow" in a separate table for the few objects that exceed the
# limit, but if anyone has any better ideas, I'd love to hear them. 

	The most common way I've seen (and done) is to put the stuff in a
table with an id, a sequence number, and the data you want to store.  I
store image data by base64 encoding it and storing the pieces in little
individual rows of about 76 characters each.  It works out pretty well
that way.

--
SA, beyond.com           My girlfriend asked me which one I like better.
pub  1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
|    Key fingerprint =  87 02 57 08 02 D0 DA D6  C8 0F 3E 65 51 98 D8 BE 
L_______________________ I hope the answer won't upset her. ____________

[prev in list] [next in list] [prev in thread] [next in thread]