Comments on: Prepared statement errors with PHP 5.3 and mysqli. call_user_func_array returns null. Type error? http://www.n8williams.com/devblog/php/prepared-statement-errors-with-php-5-3-and-mysqli-call_user_func_array-returns-null A knowledge base for simple (and beyond) web applications development Fri, 23 Jul 2010 14:03:31 +0000 http://wordpress.org/?v=2.8.6 hourly 1 By: Nate Admin http://www.n8williams.com/devblog/php/prepared-statement-errors-with-php-5-3-and-mysqli-call_user_func_array-returns-null/comment-page-1#comment-2805 Nate Admin Mon, 12 Apr 2010 03:58:41 +0000 http://www.n8williams.com/devblog/?p=144#comment-2805 Very nice! Thanks Chris. I remember running into reference issues in later php versions, things where functions required arguments that were by reference, and any fresh or deep-copy objects would show warnings or errors. Something like that. It is annoying how the ref usage is changing a bit. But for the sake of progress in php I can live with it. Oh man, I just looked at the bug. Spot on. Nice find! Using the zend framework is exactly where I ran into these errors. Very nice! Thanks Chris. I remember running into reference issues in later php versions, things where functions required arguments that were by reference, and any fresh or deep-copy objects would show warnings or errors. Something like that. It is annoying how the ref usage is changing a bit. But for the sake of progress in php I can live with it.

Oh man, I just looked at the bug. Spot on. Nice find! Using the zend framework is exactly where I ran into these errors.

]]> By: Chris http://www.n8williams.com/devblog/php/prepared-statement-errors-with-php-5-3-and-mysqli-call_user_func_array-returns-null/comment-page-1#comment-2702 Chris Mon, 29 Mar 2010 10:20:20 +0000 http://www.n8williams.com/devblog/?p=144#comment-2702 me again. it seems to be a general PHP 5.3 issue: http://bugs.php.net/43568 me again. it seems to be a general PHP 5.3 issue: http://bugs.php.net/43568

]]> By: Chris http://www.n8williams.com/devblog/php/prepared-statement-errors-with-php-5-3-and-mysqli-call_user_func_array-returns-null/comment-page-1#comment-2701 Chris Mon, 29 Mar 2010 10:18:34 +0000 http://www.n8williams.com/devblog/?p=144#comment-2701 got a workaround. all bindings MUST be references to some other thing. i solve this like so: //$arr = array_merge(array(&$statement, &$fmt), &$args); // stopped working in 5.3 $arr = array(); $arr[] = $statement; $arr[] = $fmt; foreach($args as $k => $v) $arr[] = &$args[$k]; // *ref* is REQUIRED; array_merge doesn't do that got a workaround. all bindings MUST be references to some other thing. i solve this like so:

//$arr = array_merge(array(&$statement, &$fmt), &$args); // stopped working in 5.3
$arr = array();
$arr[] = $statement;
$arr[] = $fmt;
foreach($args as $k => $v)
$arr[] = &$args[$k]; // *ref* is REQUIRED; array_merge doesn’t do that

]]> By: Nate Admin http://www.n8williams.com/devblog/php/prepared-statement-errors-with-php-5-3-and-mysqli-call_user_func_array-returns-null/comment-page-1#comment-2295 Nate Admin Wed, 20 Jan 2010 06:22:09 +0000 http://www.n8williams.com/devblog/?p=144#comment-2295 Unfortunately I never found a work-around to use a variable number of params. Which is still frustrating considering mysqli is the improved mysql library, and 5.3 is the later and improved version of php. You would think more people would have this issue. I wonder if it is a variable length function problem. Maybe you can't use call_user_func_array for functions with varable length parameters as a result of a bug or some misunderstanding on my part. Let me know if you find the solution so I can get link to it and get an unresolved problem off the google search results. I ended up recompiling php for snow leopard to be 5.2.8, since I had to recompile it anyways for an image library. And at work we switched to ruby on rails for a backend, so I don't think I'll be solving this one. Unfortunately I never found a work-around to use a variable number of params. Which is still frustrating considering mysqli is the improved mysql library, and 5.3 is the later and improved version of php. You would think more people would have this issue. I wonder if it is a variable length function problem. Maybe you can’t use call_user_func_array for functions with varable length parameters as a result of a bug or some misunderstanding on my part.

Let me know if you find the solution so I can get link to it and get an unresolved problem off the google search results.

I ended up recompiling php for snow leopard to be 5.2.8, since I had to recompile it anyways for an image library. And at work we switched to ruby on rails for a backend, so I don’t think I’ll be solving this one.

]]> By: Emil http://www.n8williams.com/devblog/php/prepared-statement-errors-with-php-5-3-and-mysqli-call_user_func_array-returns-null/comment-page-1#comment-2284 Emil Sun, 17 Jan 2010 22:17:16 +0000 http://www.n8williams.com/devblog/?p=144#comment-2284 Hi, Great post, I recently ran into this same bug, while trying to make a call to mysqli_stmt_bind_param using call_user_func_array. Have you found any solution that will still allow to bind a variable number of parameters? Thanks, Emil Hi,

Great post, I recently ran into this same bug, while trying to make a call to mysqli_stmt_bind_param using call_user_func_array. Have you found any solution that will still allow to bind a variable number of parameters?

Thanks,

Emil

]]>