Received: from mail1.bctel.ca (mail1.bctel.ca [207.194.28.67]) by hub.org (8.9.2/8.9.1) with ESMTP id XAA06732 for ; Mon, 1 Feb 1999 23:51:13 -0500 (EST) (envelope-from gburnham@sfu.ca) Received: from lucie (a3a13627.sympatico.bconnected.net [209.53.8.141]) by mail1.bctel.ca with SMTP id UAA17717; Mon, 1 Feb 1999 20:51:04 -0800 (PST) Message-ID: <014601be4e66$a596b260$8d0835d1@bconnected.net> Reply-To: "Gregory W Burnham" From: "Gregory W Burnham" To: Subject: More about large objects Date: Mon, 1 Feb 1999 20:43:44 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 According to the postgresql docs, (at http://looking-glass.usask.ca/postgresql/docs/postgres/largeobjects.htm) Originally, Postgres 4.2 supported three standard implementations of large objects: as files external to Postgres, as UNIX files managed by Postgres, and as data stored within the Postgres database. It causes considerable confusion among users. As a result, we only support large objects as data stored within the Postgres database in PostgreSQL. --------------- Now I'm confused. From what I'd gather from earlier today, Postgres used external files. Are the docs that out of date? Gregory W Burnham Software Engineer Excite Labs Faculty Of Education Simon Fraser University Vancouver, BC, V5A 1S6 604 291 3615 (ph) 604 291 5679 (fx)