On Mon, Mar 06, 2006 at 10:03:10PM +0100, Julius Hacker wrote:
> Curt Zirzow wrote:
> >
> > I assume your loop is something like:
> > while(condition) {
> > $auction_parts['id'] = 'some value';
> > $auction_parts['name'] = 'some value';
> > ...
> > $insert->execute();
> > }
> >
> Yes, thats it.
>
> > My first guess would be, if not aleady done, initialize
> > $auction_parts before you do your bind_param() with something like:
> >
> > $auction_parts = array('id' => null, 'name' => null, ...);
> > $insert->bind_param("issdsis", $auction_house["id"], ...);
> >
> Unfortunately it helps nothing :-(
Ok, i didn't really think it would but might have shown a obvious
bug with mysqli.
According to your original post it was odd that the update prepared
statment didn't complain about a NULL value, but the insert did,
and it does seem to be related to bind_param and prepare.
What are your versions of:
php?
mysql_client php is built with?
mysql server you are connecting to?
> But I think also that it's something because of the declaration and
> initalization of the variables because it works if I have the bind_param
> in the loop after I gave the variables their values.
> But to have the bind_param in the loop isn't the best solution I think.
agreed.
Curt.
--
cat .signature: No such file or directory
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
