Re: [INTERFACES] Large objects, why not use the filesystem? - Mailing list pgsql-interfaces

From Gene Selkov Jr.
Subject Re: [INTERFACES] Large objects, why not use the filesystem?
Date
Msg-id 199902010717.BAA11039@mail.xnet.com
Whole thread Raw
In response to Re: [INTERFACES] Large objects, why not use the filesystem?  (Adam Haberlach <haberlaa@ricochet.net>)
List pgsql-interfaces
> > 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.
>
>     Because the database is in a different room then the client.
>
There are lots of easier ways to pass files from that room (http, etc.)

--Gene

pgsql-interfaces by date:

Previous
From: Stefan Hornburg
Date:
Subject: ERROR: RestrictionClauseSelectivity: bad value -1.998477
Next
From: "Gene Selkov Jr."
Date:
Subject: Re: [INTERFACES] Large objects, why not use the filesystem?