Received: from mail.phoenixcolor.com (www.phoenixcolor.com [206.102.93.34]) by hub.org (8.10.1/8.10.1) with ESMTP id e6KBB1h50711 for ; Thu, 20 Jul 2000 07:11:01 -0400 (EDT) Received: from phoenixcolor.com (thor [172.16.0.210]) by mail.phoenixcolor.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id HAA13402 for ; Thu, 20 Jul 2000 07:17:55 -0400 Message-ID: <3976DD91.A1E6E776@phoenixcolor.com> Date: Thu, 20 Jul 2000 07:08:01 -0400 From: John Thorhauer Organization: Phoenix Color Corporation X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: postgres-inter Subject: Re: jdbc large object support ?? References: <1B3D5E532D18D311861A00600865478CF1B114@exchange1.nt.maidstone.gov.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200007/163 Peter Mount wrote: > > Large Objects have been supported for years - just not via streams. > > Stream support is simply passing an InputStream (say from a file) directly > to a large object in the database. The ImageViewer example shows the other > two ways, using setBytes() and using our own extensions. I tried the setBytes method and it worked great! Thanks for the help. However, I have another question. If I understand correctly I can use the setBytes() method or the getLargeObjectAPI() method. Is one preferred over the other? Does either have any distinct problems that I should be aware of? I know these are real general questions but I am trying to make sure that I start off going in the right direction with this stuff ;-) Thanks again, John -- ******************************** ** John Thorhauer ** jthorhauer@phoenixcolor.com ********************************