Re: psqlodbc versioning - Mailing list pgsql-odbc

From Dave Page
Subject Re: psqlodbc versioning
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E40C38D9@ratbert.vale-housing.co.uk
Whole thread Raw
In response to psqlodbc versioning  (Mark Slagell <ms@iastate.edu>)
Responses Re: psqlodbc versioning
List pgsql-odbc

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Mark Slagell
> Sent: 07 July 2004 20:39
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] psqlodbc versioning
>
> Can someone explain the versioning convention I see here:
>
>    ftp://ftp8.us.postgresql.org/postgresql/odbc/versions/src/
>
> Is 7.2.5 current?  The 07.03.0200 has a later file date

07.03.0200 is current. We changed to using ODBC notation for the version
which includes leading zeros and adds a couple on the end.

WRT to the lock issue, I haven't checked, but I suspect that the driver
doesn't report it because PostgreSQL simply waits for it to clear before
continuing (or detecting a deadlock and aborting the transaction). I'm
not sure that the driver is supposed to report it off the top of my head
though.

Regards, Dave.

pgsql-odbc by date:

Previous
From: Mark Slagell
Date:
Subject: Re: psqlodbc versioning
Next
From: john@intelligentapps.com (Local Cuber)
Date:
Subject: Emergent: get table names from SageLine50 by ODBC