From: Matthew Hagerty <matthew@wolfepub.com>
To: pgsql-interfaces@postgreSQL.org
Subject: Large objects, why not use the filesystem?
Date: Sun, 31 Jan 1999 15:26:15 -0500
Message-ID: <4.1.19990131151130.00a91180@firebat.wolfepub.com> (raw)
Greetings,
I always see posts of people trying to get their large binary and text
objects into and out of the database somehow. I was wondering if there is
some reason why just storing a filename in the table would be a bad thing?
This way you can let the file system worry about storing the data (since
that is what the file system is good at.) I understand that you probably
could not access the data via ODBC, but if you are writing your frontend in
C or Perl, etc. then you would simply use the filename stored in the table
to access the data.
Comments?
Also, could someone explain varchar? I have never found a *really* clear
explanation and I'm not sure I fully understand its potential, use, and/or
shortcomings.
Thank you,
Matthew Hagerty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: matthew@wolfepub.com
Subject: Re: Large objects, why not use the filesystem?
In-Reply-To: <4.1.19990131151130.00a91180@firebat.wolfepub.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox