Message-ID: <004a01bf4ca6$51fed300$6464a8c0@kpi.com.au>
From: "Joe Shevland" <shevlandj@kpi.com.au>
To: "Eliot Cline" <eliotcline@hotmail.com>, <pgsql-interfaces@postgreSQL.org>
References: <19991221074723.89113.qmail@hotmail.com>
Subject: Re: [INTERFACES] ODBC, large objects and tracing
Date: Wed, 22 Dec 1999 09:59:39 -0800
Organization: KPI Logistics Pty Ltd
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

---- Original Message -----
From: "Eliot Cline" <eliotcline@hotmail.com>
To: <pgsql-interfaces@postgreSQL.org>
Sent: Monday, December 20, 1999 11:47 PM
Subject: [INTERFACES] ODBC, large objects and tracing


> Hi,
>
> I am porting an application from Win NT to Linux. It is an application for
> storing, querying, subsetting and exporting geographic data. On NT the
data
> is stored in MS SQL Server, database access is handled through a dll which
> handles all requests for data from the application. The dll is written
using
> ODBC 3 as the interface to SQL Server.
>
> I installed postgresql 6.53 a few days ago and had a go at getting the dll
> code working with the postgresql odbc driver. As the driver is written for
> odbc 2.0, I decided to try the UnixOdbc driver and driver manager. Using
> their package my code compiled perfectly, with NO modifications.
>
> However, I immediatley ran into trouble when inserting into large-objects
> (Lot's of blobs in this app!). In the server trace there was an error to
the
> effect of "Invalid large object descriptor".
>
> That had me stumped until yesterday, when I ran across a patch for the
ODBC
> driver on this mailing list (dated Dec. 8, 99). I applied the patch (by
> hand) to the UnixODBC version of the postgres driver, and the problem went
> away. I'm impressed! I thought it was going to be way more difficult than
> this.
>
> If anyone is interested, I would be happy to supply the modified source
> files for the driver and a script I cobbled together to add the large
object
> support functions, data type and table trigger (for deleting lo's). It all
> seems to work quite well.
>

I'd definitely like to have a look at the script that was cobbled together
to add all that... I've been having troubles but its with the JDBC driver
and large objects, but I think its just that I haven't done all thats
necessary on the postgres side to enable it.


Cheers,
Joe.