PHP 5 & MySQL 5 Together? Problems?

From my experience, MySQL 5 still seems to have a few stability issues compared to version 4 - but it should work perfectly with PHP5 unless the host has screwed up a setting somewhere during installation...

It would seem that when they did the upgrade the table pm_events was completely removed. It is no longer present on any of the four sites my client has hosted with them (Omnis). And they keep passing the buck and they are not owning up to the fact that whatever happened was the result of thier upgrade.

Hmmmm... tough one. Upgrading shouldn't have caused any tables to be deleted as far as I know. If the **** up had been that severe it would have more likely deleted everything! I assume your client hasn't been taking any backups?

It's possible but at the same time impossible to say, not knowing exactly how they have the server setup.

How do you switch between 4 and 5? On my hosting you use .php for php4 and .php5 files if you want php5 and it works flawlessly.

At the end of the day I don't think you'll be getting the table back, so you'll be best just to set it up again and start from scratch.

Of course, any intelligent host would have made a complete backup before upgrading... the table might still be available.

Well it looks like they have found the issue....

Dear Customer:

I've discovered the problem. With the installation of MySQL 5, the
word 'repeat' is now a reserved word. The pm_events table contains a
field named 'repeat' so the SQL being executed to insert a new event
is failing. Is there a new version of pMachine?

Only the (site name) account is missing the table. During the
re-installation of pMachine, the SQL to re-create the pm_events table
failed because it tries to create a field named 'repeat'. Because
that is now a reserved word, the field can not be named 'repeat' so
the create table command failed.

If a new version of pMachine is not available, the hack is to wrap
the field name in all the queries with backticks (`). For example, on
(site name)/cp/events.cp.php on lines
418 and 419 the insert into the table is:

$query = new DB_query($DB, "insert into $db_events
(id,link_id,repeat,t_stamp,year,month,day,show_time,title,description)
values

('','$link_id','$repeat','$t_stamp','$evyear','$evmonth','$evday','$show_time','$title','$description')");

If you change it to:

$query = new DB_query($DB, "insert into $db_events
(id,link_id,`repeat`,t_stamp,year,month,day,show_time,title,description)
values

('','$link_id','$repeat','$t_stamp','$evyear','$evmonth','$evday','$show_time','$title','$description')");

The insert will work. Any place the repeat field name is used, wrap
it in backticks.

Son of a *****

It looks like they didn't just upgrade MySQL - they reinstalled it from scratch and then re-imported the data. Looks to me like they didn't bother reading the error messages or had them set to ignore during the import - MySQL would definitely have flagged that up as a problem.