adjroth — Mon, 17 Dec 2007 05:17:55 +0000

I've been able to figure it out, there wasn't a problem with the script or database at all, there was a very short delay in saving all the data to the database. I fixed it by adding a 500ms pause in the script.

JeevesBond — Thu, 13 Dec 2007 13:14:34 +0000

Quote: Each line printed like it should, and after each INSERT statement, it showed no errors, with 1 row affected.

Probably time to contact your hosts then. You could also try to repair the databases and rebuild indexes, have you got SSH access? I usually run something like:

mysqlcheck -cep -u<username> --auto-repair <database_name>
mysqlcheck -op -u<username> --auto-repair <database_name>

'
This has rescued me in the past. A quick scan of your code doesn't reveal any obvious errors, particularly since it was working before the hosts did an upgrade.

adjroth — Wed, 12 Dec 2007 19:25:30 +0000

I added START TRANSACTION; and COMMIT; to try to get it to work, doesn't work without them either.

I did make it print each transaction when i ran the script, along with mysql_error(), and mysql_affected_rows(). Each line printed like it should, and after each INSERT statement, it showed no errors, with 1 row affected. Each time, they weren't permanently saved and a select statement would only select the last row that was done.

like i said, it just stopped working after an upgrade was done to the servers.

Patrick A Baer — Wed, 12 Dec 2007 16:57:04 +0000

Have you tried to print the INSERT-command and checked what it actually does?

pr0gr4mm3r — Wed, 12 Dec 2007 14:55:59 +0000

I've never used the START TRANSACTION; and COMMIT; commands before. Have you tried it without them?