From: | "postgresql" <pgsql(at)symcom(dot)com> |
---|---|
To: | "Hunter, Ray" <rhunter(at)enterasys(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Large Objects |
Date: | 2002-02-27 21:07:20 |
Message-ID: | 20020227204913.A691E476187@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Ray,
A large object is simply a large amount of data. Like a tif file or any
other data that you would like to store. Personally, I would not store a
large object in the database. Instead, use the locale hard disk and refer
to the path to the object. Your front end would receive the path and
request the OS for the file.
ted
-----Original Message-----
From: "Hunter, Ray" <rhunter(at)enterasys(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Date: Wed, 27 Feb 2002 08:45:54 -0500
Subject: [SQL] Large Objects
> 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...
>
>
> Thanks,
>
>
> Ray Hunter
> Firmware Engineer
>
> ENTERASYS NETWORKS
>
> Phone: 801 887-9888
> Fax: 801 972-5789
> Email: rhunter(at)enterasys(dot)com <mailto:rhunter(at)enterasys(dot)com>
> www: www.enterasys.com <http://www.enterasys.com>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Langille | 2002-02-27 21:30:58 | Re: How slow is DISTINCT? |
Previous Message | Gregory Wood | 2002-02-27 19:14:02 | Re: System Messages |