Christoph M. Becker 16db4d1462 Fix #69975: PHP segfaults when accessing nvarchar(max) defined columns ... The SQL Server Native Client 11.0 and maybe other ODBC drivers report NVARCHAR(MAX) columns as SQL_WVARCHAR with size 0. This causes too small a buffer to be emalloc'd, likely causing a segfault in the following. As we don't know the real size of the column data, we treat such colums as SQL_WLONGVARCHAR. The related bug #67437 suggests that some drivers report a size of ~4GB. It is not certain that this is really the case (there might be some integer overflow involved, and anyway, there has been no feedback), so we do not cater for this now. However, it would not be hard to treat all sizes above a certain threshold in a similar way, i.e. as SQL_WLONGVARCHAR.		2015-07-03 00:15:47 +02:00
..
bug60616.phpt	test fixes	2015-04-04 21:42:08 +02:00
bug68087.phpt	revert skipif, this should run everywhere	2015-04-04 21:42:43 +02:00
bug69354.phpt	added test for bug #69354	2015-04-04 21:42:51 +02:00
bug69975.phpt	Fix #69975: PHP segfaults when accessing nvarchar(max) defined columns	2015-07-03 00:15:47 +02:00
config.inc
odbc_columnprivileges_001.phpt
odbc_columns_001.phpt	Corrected patch for bug #60616	2014-07-30 02:28:31 +00:00
odbc_data_source_001.phpt
odbc_exec_001.phpt	test fixes	2015-04-04 21:42:08 +02:00
odbc_exec_002.phpt
odbc_free_result_001.phpt	test fixes	2015-04-04 21:42:08 +02:00
odbc_tables_001.phpt
skipif.inc