<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Prepared statement errors with PHP 5.3 and mysqli. call_user_func_array returns null. Type error?</title>
	<atom:link href="http://www.n8williams.com/devblog/php/prepared-statement-errors-with-php-5-3-and-mysqli-call_user_func_array-returns-null/feed" rel="self" type="application/rss+xml" />
	<link>http://www.n8williams.com/devblog/php/prepared-statement-errors-with-php-5-3-and-mysqli-call_user_func_array-returns-null</link>
	<description>A knowledge base for simple (and beyond) web applications development</description>
	<lastBuildDate>Sat, 20 Mar 2010 19:29:00 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nate Admin</title>
		<link>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</link>
		<dc:creator>Nate Admin</dc:creator>
		<pubDate>Wed, 20 Jan 2010 06:22:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.n8williams.com/devblog/?p=144#comment-2295</guid>
		<description>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&#039;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&#039;t think I&#039;ll be solving this one.</description>
		<content:encoded><![CDATA[<p>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&#8217;t use call_user_func_array for functions with varable length parameters as a result of a bug or some misunderstanding on my part. </p>
<p>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.</p>
<p>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&#8217;t think I&#8217;ll be solving this one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil</title>
		<link>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</link>
		<dc:creator>Emil</dc:creator>
		<pubDate>Sun, 17 Jan 2010 22:17:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.n8williams.com/devblog/?p=144#comment-2284</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>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?</p>
<p>Thanks, </p>
<p>Emil</p>
]]></content:encoded>
	</item>
</channel>
</rss>

