psqlODBC release notes

psqlODBC 09.05.0100 Release (NOT RELEASED YET)

1. Use libpq for all communication with the server
   
Previously, libpq was only used for authentication. Using it for all communication lets us remove a lot of duplicated code. libpq is now required for building or using libpq.
2. Remove support for protocol versions older than 3.
   
Protocol version 3 was introduced in PostgreSQL 7.4, so this means that we no longer support server versions 7.3 or older. This simplified the code, making maintenance easier.
3. Remove support for ODBC versions older than 3.51.
   
The official binaries have been compiled in 3.51 mode for a very long time, so this has no effect on the official binaries.
4. Avoid one round-trip to the server when establishing connection.
   
When connecting to a server, the driver used to issue a query to determine the client_encoding setting being used, but that was unnecessary because all supported server versions send that information as part of the connection handshake when a connection is established. Remove the extra query, which should make connecting over a high-latency link faster.
5. Report max length of 'name' fields correctly.
   
PostgreSQL columns of type 'name', used e.g. in catalog tables to hold names of relations and other objects, were reported as having type VARCHAR(64). However, the real max length of a name field is only 63 bytes.
6. Remove 'Optimizer' configuration option
   
You can use the generic ConnSettings option with value "set geqo=off", to disable GEQO.
7. Fix title in 32-bit Unicode drivers setup dialog
   
The title on the 32-bit Unicode drivers's setup dialog on Windows incorrectly said "ANSI".
8. Don't export private symbols that are not part of the ODBC interface
   
This was causing problems when the driver was loaded together with another dynamically loaded library with a function of the same name. This was reported to happen when loading the odbc_fdw foreign data wrapper into a PostgreSQL server, because both the PostgreSQL server and the ODBC driver contain a function called check_client_encoding().
9. Report a sensible SQL_DESC_OCTET_LENGTH value for result set columns of type 'unknown'
   
If a query returns a column of type 'unknown', as happens e.g. in a query like "select 'foobar' from table" where the datatype of the constant 'foobar' is not specified, the SQL_DESC_OCTET_LENGTH property of the column was returned as invalid. Report it the same as 'varchar' field with no explicit length, instead.
10. Fix quoting bugs in sending integer query parameters to server
    
The drivers used to assume that if a parameter's SQL type is SQL_INTEGER or SQL_SMALLINT, the value does not require quoting when its send to the server. For example, "SELECT ?", with parameter 123 was translated to "SELECT 123", when UseServerSidePrepare was not enabled. However, there was no check that the query parameter in fact contained a valid integer, when replacing the parameter markers with their values. Also, in a query like "SELECT 0-?", a negative value needs to have parens around it, as in "SELECT 0-(-123)".
11. Don't reset autocommit when a connection is established
    
If autocommit is disabled on a connection, by calling SQLSetConnectAttr(SQL_ATTR_AUTOCOMMIT, SQL_AUTOCOMMIT_OFF, 0), before connecting with SQLDriverConnect(), autocommit was incorrectly reset back to on when the connection was established.
12. Send datatype information for query parameters, when known
    
If a query parameter is bound with a specific SQL type, pass on that information to the server. This makes the behaviour of queries like "SELECT '555' > ?" more sensible, where the result depends on whether the query parameter is interpreted as an integer or a string.
13. Use libpq defaults for Server, Username and Database settings
    
Server, Username and Database settings can now be left empty, in which case the corresponding libpq defaults will be used. The libpq default is to connect to a local server over Unix domain sockets (on Unix systems) or to localhost over TCP/IP (on Windows), if Server is left empty. The default username is the current operating system user, and the database to connect to is a database with the same name as the user. These built-in defaults can be changed by environment variables, however. This is particularly useful for connecting to a local installation via Unix domain sockets, as that is the default when Server is left empty, and was difficult to configure otherwise.
14. Fix bug in parsing E'' literals
    
The driver needs to parse a query string to determine whether a '?' character is a parameter marker, or if it's inside a quoted string or a SQL comment. This parsing did not correctly handle E''-style strings.
15. Remove 256 byte limit on the length of NOTICE messages
    
There was a built-in limit of 256 bytes on the length of NOTICE messages received from the server. Strings larger than 256 bytes were not returned to the application. That limit has been removed.
16. Fix parsing of strings containing escaped quotes with Parse=1
    
This fixes issues in extracting metadata like result set column names, with the Parse=1 option.
17. Fix connecting with a user or database name that contains spaces or quotes
    
User and database names were not quoted correctly when building a connection string. A different method is now used for sending those parameters, which doesn't require quoting and escaping.
18. Remove support for so-called "premature execution"
    
Premature execution was a method for getting information about a result set of a query, before SQLExecute() was called. That was always dangerous, as any side-effects of the query would happen, even if the application did not call SQLExecute() after all. With protocol version 3, there is a safer way to do this. This also removes the DisallowPremature configuration option, as the driver never does premature execution anymore.
19. Fix buffer overrun when the server reports an error message longer than 4096 bytes
    
If the server returned an error longer than 4096 bytes, we would overrun the buffer by two bytes. If you're unlucky, that could lead to a crash. That consistently happened on Windows.
20. Improve parsing of INSERT INTO statements, for @@identity support
    
The code that parses INSERT INTO statements, to extract the name of the target table, got confused by values containing dots, and other things. Improve the parsing support to handle a wider range of INSERT statements.
21. Fix crash in SQLTables() function, if search_path was set to a non-existent schema
    
The server-side current_schema() function returns a NULL if search_path is set to a non-existent schema, and the driver code was not prepared for a NULL result.
22. Fix buffer overrun when connecting, and KeepaliveTime and KeepaliveInterval were both set
    

psqlODBC 09.03.0400 Release

1. Rip out broken retry/timeout logic in SOCK_wait_for_ready.
   
At a quick glance, the logic looked like retry with progressive timeout, but it was horribly broken. First of all, the timeout was only used if retry_count was passed as 0. And in that case, the timeout was 0. So retry_count == 0 actually meant "check if data can be read/written without blocking", while retry_count > 0 meant "sleep until data is available". There was also some code to handle retry_count < 0, but that was dead code because none of the callers passed a negative value. The hardcoded max. retry count of 30 retries was quite bogus too. Filling the output buffer more 30 times is not necessary an error, and it's not clear that the ssl library could not return SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE more than 30 times. Unlikely, yes, but possible. So, just rip out the retry_count and progressive timeout logic. Replace the retry_count argument with a simple "should block?" argument. I didn't dare to remove the condition that we always wait if SSL is enabled, although I don't understand that at all. But perhaps there's some well-hidden reason for that. Per report from Prakash Itnal, although this just removes the broken code, and won't enable the kind of a timeout that he wanted.
2. Clean up Windows makefiles.
   
Get rid of the CPU and CPUTYPE variables in win64.mak. Instead, assume that the TARGET_CPU variable has been set correctly in the environment. TARGET_CPU is set by "setenv" script that comes with the Microsoft Visual Studio C compiler package. It never worked to pass a "CPU=x86" and using a x64 compiler, for example, so seems better to determine the correct target from the environment, than fail with a cryptic error message if the CPU argument and the environment don't match. To build 32-bit binaries with win64.mak, simply do "setenv /x86" before running "nmake -f win64.mak". Similarly, to build 64-bit binaries, use "setenv /x64". It should now be possible to build both 32-bit and 64-bit binaries with win64.mak. Ideally, we could now remove win32.mak altogether, but there are small differences between win64.mak and win32.mak in the build options that they use. I don't understand the differences enough to dare to remove win32.mak yet. The CPU=AMD64 alias for x64 is no longer supported (as the whole parameter is now gone). Also do whitespace & other cosmetic fixes to win32.mak and win64, to make them more similar. This helps when comparing the two with "diff". Remove remains of the long-gone "MULTIBYTE" setting (it was misspelled in win64.mak, anyway)
3. Fix crash if connection is closed while sending a query to the server.
   
Some functions reset conn->sock to NULL on a socket error, so we must not keep a copy of it in a local variable. Also, SOCK_get_id should check for NULL argument like all the rest of the SOCK_get/put_* functions.
4. Rewrite the conversion functions between strings and SQL_NUMERIC_STRUCT.
   
Aside from making the functions more readable and faster, this fixes a number of bugs:
1. When converting a large number from decimal to binary, the least significant byte might be wrong.
   reported by Walter Couto.
2. In binary->decimal conversion, a number with small precision but large scale caused a "Floating point exception".
   
3. In binary->decimal conversion, building the final string was wrong, picking up "digits" from outside the reserved stack space, if scale was larger than 40
   
4. The param_string buffer allocated for the result of binary->decimal conversion was too small.
   
Also add a test cases for all of these bugs.
5. Fix ODBC function escape for SPACE function.
   
6. Make sure that the psqlodbc ANSI driver is ODBC3.5.
   
7. Register 64bit XA DLL on installation
   
Changes by a patch from Craig Ringer
8. Fix potentially uninitialized local pointer access which causes.
   
fatal compilation errors on vs2012/2013 reported by Craig Ringer.
9. Fixed ctype_length() is missing the length for SQL_C_BIGINT and SQL_C_NUMERIC.
   
patch by John Smith.
10. Fix access to unallocated memory in IAsyncPG.
    
IAsyncPG was deleting its self, then returning an instance variable by value. This is probably going to be safe pretty much all the time, but it's still a memory error, and DrMemory (a Windows valgrind-alike)
11. SQL_NUMERIC_STRUCT was not available until ODBC 3.0.
    
Also add a prototype for ResolveNumericParam for readability.
12. Increase digits used to convert from REAL/DOUBLEs to strings so that the reverse conversions can recover original values.
    
Patch originally by John Smith.
13. Clear errors for prepared statement for subsequent exections.
    
14. Fix the problems using SQLFetch on prepared INSERT with RETURNING clause.
    
reported by John Smith.
15. Fix use of server-queried version before connection.
    
psqlODBC attempted to use the version that's queried from the server before it was obtained from the server during the connection setup. Because the server version is initialized to 0.0, tests for "server version >= 7.4" or "server version >= 6.4" using the PG_VERSION_LT macro were always returning false. Instead, use PROTOCOL_64 and PROTOCOL_74 tests against conninfo. These don't offer any "greater than" form, so just test both. There's little point adding anything prettier when it can all be removed when v1/v2 protocol support is removed soon anyway. The main symptom of this issue was that psqlODBC was sending an invalid protocol message for the v3 protocol, "Q \0", causing the server to wait for the second half of the length word forever. At connection close, the server would emit:
  unexpected EOF within message length word
This issue was observed while tracking down problems with XA transactions in MSDTC failing to commit after a successful prepare because an isolated tx created via getLockedXAConn() got stuck here, but is not confined to that problem.
16. Don't use PG_VERSION_xx() macros in original_CC_connect().
    
it's not obtained from the server yet. This may fix another cause of the problem Craig Ringer reported.
17. Fix bug in SQLCancel().
    
If one thread was busy executing a savepoint statement, while another thread calls SQLCancel() on the statement, SQLCancel() would try to release the locks held by the other thread. That's extremely racy; if the other thread tries to increment/decrement the lock_CC_for_rb counter at the same time, we could end up releasing the lock to many times or too few times. Also, releasing a pthread mutex from a different thread than the one who acquired it is undefined behavior. AFAICS the DiscardStatementSvp() call in SQLCancel() can be safely removed. It's outright wrong and dangerous if the statement is busy executing in a different thread, and the other codepaths in PGAPI_Cancel() already call DiscardStatementSvp(). Bug report by Jade Koskela.
18. Fixes a NULL pointer dereference occurring when connecting.
    
using SSPI authentication (without kerberos, a local Windows user trying to connect to postgres instance on same host). Patch originally by Nikhil R Deshpande.
19. Fix bug with UseDeclareFetch=1 when a transaction is committed before fetch.
    
If a server cursor is closed before the application has fetched any rows from the result set, the "base" of the result set's cached rowset was off-by-one. Also add a regression test for the same. This fixes the bug reported by Jan-Peter Seifert.
20. Fix driver name mismatch between 32-bit ODBC app and 64-bit MSDTC host.
    
If the 32-bit driver runs on a 64-bit host within a 32-bit app running under SysWow64 then XA transactions will fail to recover. That's because recovery is done by pgxalib.dll which runs with in MSDTC.exe - a 64-bit application. It connects to a DSN supplied by psqlODBC in EnlistInDtc_1pipe during DTC enlistment by the XA resource manager. This DSN uses the driver name of the client's ODBC driver - which is fine so long as the client and MSDTC architectures match. If they don't then MSDTC will fail to connect to Pg, so it'll never resolve transactions. Traces of MSDTC will show RM_COMMIT_DELIVERY_FAILED_DUE_TO_CONNECTION_DOWN events. Traces of pgxalib.dll will show xa_recover(..) being entered, followed by "SQLDriverConnect return=-1".
21. Remove PgDtc_set_property(.., prepareRequestded, 0) which causes a crash in case PREPARE TRANSACTION error.
    
The property prepareRequested isn't set anywhere.
22. Add KeepaliveTime and KeepaliveInterval options to specify time or interval for keepalive.
    
23. Fix a memory leak check qresult.
    
Per report by Pluto Cobain.
24. Get rid of copy and paste code in installer/ and unify them.
    
The powershell scripts had lots of duplication. Make the unified code instead. Original patch was provided by Craig Ringer.
25. Clear unused stuff from PgDtc_isolate() function.
    
Also add CC_initialize_pg_version() call after CC_copy_conninfo() so as to avoid the trouble caused by early PG_VERSION_xx() calls.
26. Fix race condition in getting the current decimal separator.
    
The code to get the current decimal separator was not thread-safe. If two threads concurrently saw that the locale had changed, they might both try to free() the same string. This isn't a perfect fix, there's still a race condition if a thread changes the locale while another thread is running the psqlodbc code. But at least this eliminates the race condition when the locale was changed earlier, not concurrently, and even if it is changed concurrently, this is less likely to crash, depending on the way localeconv() is implemented in libc.
27. Fix bug in building an abbreviated connection string.
    
Introduced by the keepalive-patch, which accidentally removed a line from sprintf format string. Caught by a compiler warning.
28. Fix buffer overflow in SQLGetData.
    
If a PostgreSQL timestamp column is fetched using SQLGetData, into a SQL_C_CHAR output variable, with size of 20-22 bytes, the driver might overrun the buffer by a few bytes with unusual timestamp values, with year < 0 or > 10000. While at it, fix the truncation behavior for date/time/timestamp values so that if the output buffer is too small, we still write what fits and truncate, instead of writing nothing. This is something that one might do on purpose, e.g. if you only want to fetch the year part of a date, you might call SQLGetData() on a date column, with only 4 bytes long output buffer. (although we haven't heard any complaints from the field). Also, if the output buffer is of type SQL_C_WCHAR, but the buffer length is odd, and we have to truncate, we didn't NULL-terminate the string. Using an odd-sized buffer with SQL_C_WCHAR is a pretty unlikely thing to do, but nevertheless I think this is more correct behavior.
29. The function SC_setInsertedTable() prepares an info for subsequent 'select @@IDENTITY' command.
    
Take table name like catalog.schema.table into account in the function. Fix the bug reported by Phillippe Champignon.
30. Improve pgxalib.dll(MSDTC support).
    
1. Add an option which lets xa_open() try to connect to the database immediately. This would cause an error at enlistment in dtc when the authentication method depends not only on the db user but also on the OS user, which means the automatic transaction recovery is unavailable.
   
2. Log the error message in case of SQLDriverConnect() error.
   
3. Improve the logging.
   
31. Fix the regkey search bug when XARMcreate() causes an error at enlistmentvin DTC.
    
32. Additonal improvement on MSDTC enlistment.
    
Unfortunately the current pgxalib.dll can't recover transactions which use sslmode verify-[ca|full] or whose authentication is SSPI, certificate or ident. When MSDTC.exe tries to connect to PostgreSQL it does so under Windows user NETWORKSERVICE, which won't match the username the original user connected to PostgreSQL as. So PostgreSQL will reject the connection.
33. Fix SQLTables column names to be ODBC version 3 compliant.
    
In ODBC3, TABLE_QUALIFIER was renamed to TABLE_CAT, and TABLE_OWNER to TABLE_SCHEM. Per report David Hedberg.
34. Add a new dialog page to the setup program and allow the setting of PREFERLIBPQ and XAOPT option.
    
35. Add a powershell script buildBootStrapper.ps1 which builds bootStrapper program with some optional parameters.
    
Quote the version number of bootstrapper from the configuration xml file unless specified. Also change the name of 32bit MSI in the bootstrapper according to changes of 32bit installer build system. Change buildInstallers.ps1 build the bootstrapper together. Change ALLUSERS from "2" to "1" of the 64bit installer.

psqlODBC 09.03.0300 Release

1. Fix implicit casts between SQLCHAR and char. Don't rely on -Wno-pointer-sign.
   
2. Pass the argument to isalpha/isspace etc. routines as unsigned char.
   
Per the C standard, the routine should be passed an int, with a value that's representable as an unsigned char or EOF. Passing a signed char is wrong, because a negative value is not representable as an unsigned char. Unfortunately no compiler warns about that.

3. Use "function(void)" instead of "function()" to declare 0-arg functions.
   
"function(void)" is the correct syntax in a function declaration, although in practice compilers accept the latter too. It's OK in a function definition, but change those too for consistency. This fixed by Michael Paquier.

4. Add missing function declarations.
   
These are not actually used outside of pgtypes.c, but let's be consistent and declare them in pgtypes.h This fixed by Michael Paquier.

5. Use the PG_CONFIG setting from ./configure cmd line in regression tests.
   
If compiling without libpq (configure --without-libpq), then you still need to have pg_config in path to build the regression tests, or specify PG_CONFIG at the make command line.

6. Add more test cases.
   
Add a new test case to test ODBC functions deprecated in ODBC 3.0, ODBC catalog functions, SQLGetConnectOption and Avoid deprecated SQLAllocStmt/SQLFreeStmt in regression tests. and more. Per Michael Paquier

7. Don't clear error number when SQLGetDiagRec is called.
   
Calls to SQLGetDiagRec are supposed to be nondestructive, per ODBC spec. Also add a test case for that.

8. Fix two UseDeclareFetch bugs.
   
1. NOTICE messages were not delivered to the application, if they arrived as response to the DECLARE CURSOR statement.
2. Array-bound parameters on SELECT-queries caused a "cursor already open" error.
These bugs were found by running the regression suite with UseDeclareFetch=1. It's now clean.

9. Fix crash if connection is closed during CC_send_query_append function.
   
This fixed Malcolm MacLeod

psqlODBC 09.03.0210 Release

1. SSL verify[-(ca|full)] is avaiable since 8.4.
   
There seems no need to check it. Also there's no need to call lt_dlopen currentl y.

2. Update EXTRA_DIST in Makefile.am
   
Files for the new lfconversion test case were missing.

3. Fix locking in SC_set_prepared
   
added ENTER/LEAVE_CRIT_CS calls in SC_set_prepared.

4. Add test case for CTE queries (WITH ...)
   
None of the existing test cases covered that. This test case gives a different e rror message than the original one, but it'sthe same underlying issue.

5. Silence compiler warning.
   
SQLGUID format and conn_settings cannot be NULL.
This fixed by Michael Paquier.

6. Fixed POSTGRES_RESOURCE_VERSION variable.
   
Pass the content of POSTGRES_RESOURCE_VERSION variable to the resource compiler correctly so that FileVersion and ProductVersion are properly set.

7. Change regression test positioned-update
   
Use "exit(1);" instead of "return;" to exit from main().
This fixed by Michael Paquier, at least some compiler on OS X didn't like it.

psqlODBC 09.03.0200

1. Set TCP keepalive by default.
   
2. Fix cursors test case on big-endian systems.
   
The SQL_CURSOR_COMMIT_BEHAVIOR property is a SQLUSMALLINT, not SQLUINTEGER. On a little-endian system, you wouldn't notice, provided that the target variable was initialized to 0 before the SQLGetInfo call.
Per report from Christoph Berg that the cursors test was failing on mipsel and other big-endian architectures.

3. Add regression test for SQLBindCol.
   
We were already doing SQLBindCol as part of the positioned-update test, but seems good to have one explicitly for it.

4. The driver takes SQL_C_LONG to mean SQLINTEGER rather than "long".
   
The regression test was failing on the s390x architecture because of that.
It's big-endian, with sizeof(long) == 8.

5. Revert "When LF->CR+LF conversion causes an buffer truncation, supress the conversion (in case of unicode)."
   
6. Refactor utf8_to_ucs_lf.
   
A macro is difficult to debug, so turn it into a regular function.
Also, add a new test case for LF->CR+LF conversion, to test the bug that Nils Go"sche reported (which was already fixed).

7. Add locking to SQLFreeStmt and SQLFreeHandle.
   
This fixes a race condition, where SQLFreeStmt is called while the connection is busy executing another statement.
SC_set_prepared would see that the connection is busy (CONN_EXECUTING), and not issue a DEALLOCATE statement to free the prepared statement in the backend, leaking it.

8. The 2dn argument of SC_set_prepared() is int(enum) not BOOL.
   
9. Change to supply non-NULL parameters for SC_set_error().
   

psqlODBC 09.03.0100

1. Fix uninitialized use of 'allocbuf' variable, in case of out-of-memory.
   
Compiler warned about this. If ENLARGE_NEWSTATEMENT macro ran out of memory, it would jump to cleanup routine.
The cleanup would check if allocbuf isNULL, and try to free() it if not.
allocbuf needs to be initialized to NULL before the first ENLARGE_NEWSTATEMENT macro invocation.

2. SQL_C_SLONG stands for SQLINTEGER not long.
   
3. Change SQL_ATTR_PARAMS_PROCESSED_PTR attribute which is set by SQLSetStmtAttr() from (SQLUINTEGER *) to (SQLULEN *).
   
This fixes the bug reported by Christopf Berg.
Also verify similar attributes which were changed from SQL(U)INTEGER (*) to SQL(U)LEN (*) when 64bit ODBC was introduced.

4. Reduce the memory usage of ConnectinClass objects by changing their large fixed length text fields to variable ones.
   
Because changes are applied to percent-encoded fields this time, password field is also a target of this.

5. Revise MSDTC support.
   
Remove pointlessly complicated AsyncThreads stuff. Instead use _beginthread() to clean up threads.
Make pgenlist.dll from the structure change of ConnectionClass.
The driver dlls exports the functions described in connexp.h which are used by pgenlist.dll.
Isolate the current communication path if necessary.
While an IAsyncPG object is alive, a ConnectionClass object (hereinafter refered to as conn-obj) is assigned to it.
The assignment has to be changed in the following cases.

1. SQLDisconnect() is called for the current connection handle which is assigned to an IAsyncPG object.
Allocate another conn-obj and move the current communication path (*sock* member of the current conn-obj) to the new conn-obj. The communicaation path is lost from the current conn-obj and the new conn-obj is assigned to the IAsyncPG object.

2. Another (global) transaction is about to begin but the current global transaction is not PREPARED yet.
Same as case a) but will open a new communication path for the current conn-obj for the subsequent ODBC API calls.

3. Another (global) transaction is about to begin and the current global transaction is already PREPARED.
Allocate another conn-obj and open a new communication path for the conn-obj. The new conn-obj is assigned to the IAsyncPG object only to issue COMMIT/ROLLBACK PREPARED command. communication pass (*sock* member of the current ConnectionClass object) to the new object and change the state of the current object NOT CONNECTED. The IAsyncPG object uses new object instead of the current object. In case b) the current object will open a new communication path.

6. Ignore automatically-generated files in source code with .gitignore.
   
This is useful to prevent accidental commit of files that are not wanted in the remote repository.
The original patch was provided by MichaelPaquier. I also added files genearated by VC build tools or WIX tools to .gitignore.

7. The first cut of psqlodbc setup project. It builds a setup program which can't be done by a single MSI.
   
It would install VC++ redistributable, 32 bit psqlodbc driver and 64 bit psqlodbc driver (on 64 bit windows).

8. Change the configure.ac
   
1. Change checking SIZEOF_LONG not SIZEOF_LONG_INT.
2. with_xxxxx (xxxxx is the package name) variables directly instead of the withval variable.
3. Improve the help message of configure script.
4. Stop linking lib(i)odbc library because the library is unnecessary and rather harmful.
Per report from Pavel Raiskup(postgresql.org/message-id/1769926.65KUyECjFr@nb.usersys.redhat.com).

5. Move -Wall -Wno-pointer-sign CFLAGS option specified in Makefile.am to configure.ac.
6. ODBC_CONFIG is set when neither unixODBC nor iODBC is explicitly specified.
9. Silence misc compiler warnings. Also a few comment typo and whitespace fixes.
   
10. CC_Copy is needed if _HANDLE_ENLIST_IN_DTC_ is used, regardless of CLEANUP_CONN_BEFORE_ISOLATION.
    
That caused compilation on Windows to fail.

11. Remove some dead code.(SOCK_clear_error, SOCK_skip_n_bytes)
    
12. Handle turning standard_conforming_strings to off in mid-session.
    
We already watched for a ParameterStatus response indicating that standard_conforming_strings was turned on, and acted accordingly, but if it was turned off, we did nothing.

13. Remove common.o on "make clean"
    
14. Change the default for UseServerSidePrepare to 1.
    
The docs have recommended UseServerSidePrepare=1 for server versions 7.4 onwards, so it seems prudent to change the default so that people don't needto remember to specify it manually.
With UseServerSidePrepare=1, the "insertreturning" regression test case behaves better, ie.
SQLNumResultCols() correctly returns the number of columns for an INSERT RETURNING statement, even when called before SQLExecute().

15. Remove useless 'sync' parameter from prepareParameters() function. It was always passed as TRUE.
    
16. Don't issue a BEGIN when running VACUUM in auto-commit mode.
    
Normally in auto-commit mode the driver begins a new transaction implicitly at the first statement, by sending a BEGIN statement. However, some commands, like VACUUM, cannot be run in a transaction block, and you will get an error like "VACUUM cannot run inside a transaction block" from the server. In UseServerSidePrepare=0 mode, the code looks at the first word of the query to determine if the statement is one of the special ones, and if so, didn't begin a new transaction even when auto-commit mode is disabled. However, in UseServerSidePrepare=1 mode, when using SQLPrepare/ SQLExecute to run the VACUUM, that check was not made. Fix that. There was one more related inconsistency between UseServerSidePrepare modes. Without server-side-prepares, if you issued an explicit BEGIN in auto-commit mode, the implicit BEGIN was ont sent. But without server-side prepares, it was. It seems best to send the implicit BEGIN in both cases, because then you get a warning from the backend about the second BEGIN. That's a good thing, because a sane ODBC application should be using the ODBC function SQLEndTran() for transaction control, not explicit BEGIN/COMMIT.

17. When LF->CR+LF conversion causes an buffer truncation, supress the conversion (in case of unicode).
    
18. Handle SSL client certificate authentication in Windows Schannel security support provider.
    
You have to place the certificate file postgresql.pfx (PFX or PKCS12 format) in %APPDATA%\postgresql folder instead of postgresql.crt and postgresql.key (I wasn't able to find the way to handle PEM format using Cryptography API unfortunately).
You can create the file using the following command.
openssl pkcs12 -export -in postgresql.crt -inkey postgresql.key -out postgresql.pfx (with empty password).

19. Change Windows installer build system for the next release.
    
Change to specify ProductCode for each version so as not to forget to change ProductCode in case of major version up. Remove VC runtime merge modules from the installer(runtime dlls will be installed via psqlodbc setup program).
[64bit version only] Use libpq by default Remove GSSAPI support by default

20. Concentrate the settings of Windows build system to an xml file and build binaries or installers with reference to it.
    
(configuration.xml) xml file to specify the setting of the build environment. It is automatically generated in winbuild folder as a copy of winbuild/configuration_template.xml when you invoke editConfiguration script firstly.
.winbuild/configuration.ps1 modules to handle the configuration file
.winbuild/editConfiguration.ps1 edit configuration file (GUI)
.winbuild/editConfiguration.bat same as above with a minimized console window
.buildx86.ps1 build 32bit binary
.buildx64.ps1 build 64bit binary
.installer/buildx86-installer.ps1 build 32bit installer
.installer/buildx64-installer.ps1 build 64bit installer

21. handle private keys of PEM form using CryptoAPI.
    
Certificates of PFX form are no longer needed for SSL client certificate authntication.

22. Fix a bug in CC_copy_conninfo() that free()s password item of input source unexpectedly.
    
Change CC_copy_conninfo() and copy_globals() so that they copy each item one by one.

23. Fix the newly-introduced CORR_STRCPY and CORR_VALCPY macros.
    
They were broken, did not compile. This fixed by Michael Paquier.

24. Add support for verify-ca/full sslmode using Windows Schannel Security Service Provider.
    
Root CAs must be installed into Windows Root certificate store beforehand.

25. VOID is not defined on all systems. Use void insted.
    
This fixed by Christoph Berg.

26. winres.h instead of afxres.h.
    
There are some cases (VS 2012 express etc) when afxres.h doesn't exist.

27. Avoid double-free() bug.
    
Spotted by Fortify static analysis tool.

28. Escape double-quotes in table name correctly.
    
When constructing the select/update/delete for current row in a rowset, and the schema or table name contained double-quotes, they were not correctly escaped in the constructed SQL statement. That lead to errors when doing positioned updates. Also, use snprintf and snprintf_add instead of sprintf and strcat in more places. Makes these things look less like buffer overflows to static analysis tools, and make for more readable code anyway.

29. Construct ctid string correctly for block no > 2^31.
    
Block number is unsigned. Other places where we construct ctid strings we got this right, but not this one. I'm not sure how to trigger this codepath, but I'm sure something funny would happen if you tried to use these functions on large enough tables (> 16 TB).

30. Fix buffer overflow in interval parsing.
    
Flagged by Fortify static analysis tool.

31. Check return value of stdup() for out-of-memory.
    
There are a lot of little bugs like this throughout the code, but it's start...

32. Replace calls to my_strcat and my_strcat with snprintf_add.
    
my_strcat didn't check for buffer overflow, which Fortify static analysis tool flagged as an issue.

33. Fix buffer overflow in handling of SQLTables params.
    
34. Use snprintf() instead of sprintf() for safety.
    
I believe these instances were in fact safe, because a cursor name has a maximum length.

35. bufferoverflowu.lib seems no longer needed in recent versions of VC environment.
    
removed it from win64.mak. Speocify CUSTOMLINKLIBS=bufferoverflowu.lib from the command line when it is neccessary in old VC environment.

36. Fix memset() call, meant to clear the whole struct.
    
Per compiler warning.(psqlodbc.c)

37. socket: speedup also ipv6 connection
    
Call getaddrinfo() with AI_NUMERICHOST if it is ipv4/ipv6 address. For that reason the inet_pton() is better than inet_addr().
This fixed by Pavel Raiskup

38. Call getaddrinfo() with AI_NUMERICSERV because the service is a port number.
    
39. Fixed lost mylog.h in Makefile.am.
    
This fixed by Pavel Raiskup

psqlODBC 09.02.0100

psqlODBC 09.01.0200

psqlODBC 09.01.0100

psqlODBC 09.00.0310

psqlODBC 09.00.0300

psqlODBC 09.00.0200

psqlODBC 09.00.0101

psqlODBC 09.00.0100

psqlODBC 08.04.0200

psqlODBC 08.04.0100

psqlODBC 08.03.0400

psqlODBC 08.03.0300

psqlODBC 08.03.0200

psqlODBC 08.03.0100