From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Mark Slagell" <ms(at)iastate(dot)edu>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: psqlodbc versioning |
Date: | 2004-07-08 07:13:32 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40C38D9@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Mark Slagell
> Sent: 07 July 2004 20:39
> To: pgsql-odbc(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Local Cuber | 2004-07-08 14:34:19 | Emergent: get table names from SageLine50 by ODBC |
Previous Message | Mark Slagell | 2004-07-07 20:28:00 | Re: psqlodbc versioning |