Re: [GENERAL] large object minimum storage - Mailing list pgsql-general

From Dustin Sallings
Subject Re: [GENERAL] large object minimum storage
Date
Msg-id Pine.SGI.3.95.990626200849.3570C-100000@bleu.west.spy.net
Whole thread Raw
In response to large object minimum storage  (Kenneth Been <been@cs.nyu.edu>)
List pgsql-general
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. ____________


pgsql-general by date:

Previous
From: Dustin Sallings
Date:
Subject: Re: [GENERAL] Definitive list of new types in 6.5 needed
Next
From: ralli@poboxes.com
Date:
Subject: unsubscribe