Description:
------------
It is a well-known fact that ODBC support truncates returned database keys to 31 characters. No surprise there, since the key name length is hard coded at 32 bytes in php_odbc_includes.h. And, no complaints either, since we've all learned how to live with it.

However, when "mbstring" support is compiled into PHP using "--enable-mbstring" at build time, the keys are now truncated at 15. This happens even when the server and database are set to a single-byte character set such as UTF8.

In my case, I am using mysql-5.6.14, unixODBC-2.3.2 and mysql-connector-odbc-5.2.6-src. I have set "character-set-server = utf8" in my.cnf and have set the default database character set with "alter database character set = 'utf8';" but still no joy.

The obvious fix is to recompile PHP with "char name[64];" in the odbc_result_value structure in php_odbc_includes.h. However, if it is possible, ODBC support should query the database and determine which character set is in use (e.g. the query in question under MySQL is "show variables like 'character_set_database';"). If it is an 8-byte character set, the mbstring support should be turned off and the full 31-byte keys returned. If it is not possible, I throw my vote behind changing the key length to 64 by default (regardless of the reluctance to do so as expressed in Bug #30043).