From: | Matthew Hagerty <matthew(at)wolfepub(dot)com> |
---|---|
To: | pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Large objects, why not use the filesystem? |
Date: | 1999-01-31 20:26:15 |
Message-ID: | 4.1.19990131151130.00a91180@firebat.wolfepub.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Haberlach | 1999-01-31 20:51:03 | Re: [INTERFACES] Large objects, why not use the filesystem? |
Previous Message | The Hermit Hacker | 1999-01-31 18:38:10 | psqlodbc for Win3.11 with win32s |