failing sql MUST work > mysql config question

[stevesweetland]

ok.

problems fellers.

see this sql?

CREATE TABLE `Unavailable` (
  `ID` mediumint(9) NOT NULL auto_increment,
  `ProductID` mediumint(9) NOT NULL default '0',
  `ReAvailable` varchar(64) NOT NULL default '',
  PRIMARY KEY  (`ID`,`ID`)
) TYPE=MyISAM AUTO_INCREMENT=109 ;

that dont work, because it has ID set for the primary key twice, so if i take it out, it works. Yay!

The Problem
Im running plesk. Im attempting to run a restore for an in particular client, which is fine, but the database fails. I happen to know that the reason for this the reason above.

I CANT get at the sql to modify it, so i wondered if there was any way i could configure mysql temporarily so it just accepted this anyway? i mean, the above code works on a cobalt machine we have, but just not on the real webservers...

[Sxooter]

Nope. Just one primary key.

Can't you get by with a unique instead? Are you actually saying the application is attempting to make a table with two PKs in it? Any app doing that is fundamentally broken AND retarded to boot.