That is great.
I've been using psqlodbc and missed a proper error code / sqlstate
Jonathan Fuerth wrote:
> Hello people,
> I've taken a few days to hack in support for the frontend/backend
> protocol v3.0 (which first appeared in PostgreSQL 7.4). My main
> motivator was to get at the SQLSTATE codes which backends >= 7.4
> return with every error message.
> What's done now:
> -read the new message length field from all server responses
> -Parse new-style error/notice blocks
> -return correct SQLSTATE from backend to ODBC callers (connection and
> result level)
> -added #ifdef so the driver compiles against newer iODBC headers
> What I intend to finish this week:
> -upgrade the function call API to new protocol
> What needs doing that I can't/won't finish soon:
> -upgrade Windows configuration GUI to add new "7.4" protocol option
> -take advantage of the new transaction status byte in 'Z' messages
> (my patch just ignores them)
> -rework prepared statement stuff to use the new protocol features (I
> haven't looked at this stuff at all, but the old code works on the new
> protocol--it could be faster, that's all)
> If there is any interest in this patch, I will post it to the list, or
> email it to individuals.
> -Jonathan Fuerth
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if
> joining column's datatypes do not match
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 267.5.1 - Release Date: 6/2/2005
In response to
pgsql-odbc by date
|Next:||From: Jonathan Fuerth||Date: 2005-06-03 14:35:51|
|Subject: Re: Frontend/Backend protocol 3.0|
|Previous:||From: Tim||Date: 2005-06-02 19:22:52|
|Subject: Specifying character sets in ODBC|