fix compile failure on Windows - Microsoft hasn't heard of long long :)

add a test case
fix incorrect handling of unsigned bigint.
optimize handling of unsigned int

fix more leaks. handle better unknown type (4.1.x connected to 5.0.x
incompatibility)

fix a crash and a leak.
4.1.15 (client) -> 5.x (server) because of the incompatibility because of
decimal in the protocol binding may fail. Don't close the statement in
that case because

fix a crash and a leak.
4.1.15 (client) -> 5.x (server) because of the incompatibility because of
decimal in the protocol binding may fail. Don't close the statement in
that case because subsequent ->execute() will crash or any other function
that will try to use already freed (and in debug mode thrashed) pointer.
#probably more problems exist because of the 4.1.x -> 5.x protocol
#incompatibility

show more ...

on 32bit platform if the column is UNSIGNED INT(11) and the value
is greater than 2^31-1 then convert to string. on 64bit this is of no
problem because there long inside zval is big enough to

on 32bit platform if the column is UNSIGNED INT(11) and the value
is greater than 2^31-1 then convert to string. on 64bit this is of no
problem because there long inside zval is big enough to keep unsigned
int(11)

show more ...

fixed an error in mysqli_fetch_fields (function returns NULL instead of array
when row_number > num_fields).
Thanks to Marc Deslisle and phpMyAdmin team for the report.

use proper macros and vars instead of strlen()

fix #34810 (mysqli::init() and others use wrong $this pointer without checks)

add charsetnr and length to the object returned. this is kind of bug
because fetch_fields() and fetch_field() return that info and
fetch_field_direct() does not

MFH: fix #32081 (mysqli_real_connect(): mysqli.default_socket in php.ini has no effect) for real

- Bumber up year

fix for bug #33263 (mysqli_real_escape doesn't work in __construct)

fix for bug #33090 (mysql_prepare doesn't return error)

after throwing an warning bail out

MFB

revert this one till we have a better way to inform the user where the
truncation has occured

return MYSQLI_DATA_TRUNCATED if data happens to be truncated
#the manual has to be updated

return directly

bail out when detecting incorrect number of parameters to be bound.

initialize values because the call to zend_parse_parameters may not do it

fixed memleak in mysqli_close
fixed bug #32956 (mysqli_bind_result doesn't support MYSQL_TYPE_NULL)

fix bug #32013(MySQLi bind_result causes fatal error: memory limit reached)
#this is a partial fix but it cannot be better. the user has to call
#$stmt->store_result() and for a BLOB/MEDIUTEX

fix bug #32013(MySQLi bind_result causes fatal error: memory limit reached)
#this is a partial fix but it cannot be better. the user has to call
#$stmt->store_result() and for a BLOB/MEDIUTEXT (and larger) space will be
#allocated as big as the biggest column value.

show more ...

another fix for last commit (committed from wrong tree) :(

added support for data truncation (bind_result) for MySQL 5.0.5

- nail down another 64bit problem. this will fix about 14 failing tests
on amd64 (probably other 64 bit arch).
- use ulong for this boolean variable, as it was before
- throw an warning

- nail down another 64bit problem. this will fix about 14 failing tests
on amd64 (probably other 64 bit arch).
- use ulong for this boolean variable, as it was before
- throw an warning if offset passed to mysqli_stmt_data_seek is negative

show more ...