On Fri, 9 Mar 2001, Brian Baquiran wrote:
..
> Postgres can store large objects and refer to them via their oid. For
> the SQL interface, there is a function lo_import which will take a file
> and import it into the DB. It returns the Oid. Clearly you should store
> the Oids in your own tables. There's also a lo_export function.
Oh YEAH. I stand corrected. There's that ugly interface. I suggest you
don't use it -- it's quite similar in concept (and functionality!) to the
BFILE data type, and it's CLUNKY. You try using the oid scheme from Perl
DBI, you immediately break compatibility with every other database
supported by DBI on the planet.
The Pg documentation is quite clear on this -- storing data in an oid does
not gain you any special features (e.g. indexes) and you will eventually
come to grief with the 2GB file size limit.
---------------------------------------------------------------------
Orlando Andico <[EMAIL PROTECTED]> POTS Phone: +63 (2) 848-2893
Mosaic Communications, Inc. GSM Mobile: +63 (917) 531-5893
I'm not suffering from insanity -- I'm enjoying every minute of it!!
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
