Re: Large Objects

From: Erle Czar Mantos <erle(at)hindang(dot)msuiit(dot)edu(dot)ph>
To: "Hunter, Ray" <rhunter(at)enterasys(dot)com>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Large Objects
Date: 2002-02-28 02:36:45
Message-ID: Pine.LNX.4.33L2.0202281027470.30004-100000@hindang.msuiit.edu.ph
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


Hi, Morning All:

Large objects in PostgreSQL are simply large chunks of
information which you may want to store in a database for reasons
I don't know. Example is if you want to store the actual JPEG file
in the database and not just reference it as a string and just put
it as a file in another directory. A possible reason for hiding the
actual JPEG file in a database is to hide it from your Sys Ad if those
JPEG file contains "PORNO" images (Sorry, no pun intended, it just was the
case with a friend of mine, hhehehe). Anyway, an experimental application
I know of stores geographical images as large objects in a postgresql
database. Good luck with large objects, it may sound hard but after you
get to know it, it just becomes a walk in the park.

Erle

On Wed, 27 Feb 2002, Hunter, Ray wrote:

> I have been reading the user manual for largre objects in postgres. What I
> do not understand is when and why you would use them?
>
> Can someone point me to some good documentation on this...

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Jan Oravec 2002-02-28 11:34:23 backward SQL query
Previous Message Christopher Kings-Lynne 2002-02-28 01:05:52 Re: Large Objects