SQL Patches with TYPE=MyISAM are failing

I'd dearly love to get my next website up as a v1.5.0, but I'm having issues installing SQL patches for many of the v1.5.0 compatible MODS.

My dev platform is MOWES which I've used for years. Current version using
Apache 2.2.11
PHP 5.3.5
MySql 5.5.8
Running on a win7 box

I manually created my UTF8 database using PhpMyAdmin
Installed v1.5.0 without issue - Awesome BTW.

The SQL patches fail to import in both Zencart SQL patch util and also when using PhpMyAdmin.

Any SQL patch file that starts with something similar to this fails:

CREATE TABLE notes_categories (
notes_categories_id int(11) NOT NULL auto_increment,
notes_categories_name varchar(64) default NULL,
PRIMARY KEY (notes_categories_id)
) TYPE=MyISAM;
From PhpMyAdmin I get the following error:
#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=MyISAM' at line 5
Have I got the database configured wrong or am I missing something?

TYPE=MyISAM is obsolete syntax in MySQL.

Change your code to ENGINE=MyISAM instead.

This is STILL an issue with multiple current plugins. It would be so fabulous if they worked w/o code changes ... please update this plugin authors! Perhaps am I missing some obvious reason to leave obsolete code in plugins - I'm not a programmer after all - but for me they've been failing installs that require editing for a long time.

Angeltown:

This is STILL an issue with multiple current plugins. It would be so fabulous if they worked w/o code changes ... please update this plugin authors! Perhaps am I missing some obvious reason to leave obsolete code in plugins - I'm not a programmer after all - but for me they've been failing installs that require editing for a long time.

While the rant is understandable, it would unfortunately be of more benefit in the applicable thread(s) where the code needs to be updated. For those plugins that you have worked your way through to repair, they could be submitted with the update by anyone, though ideally making contaact with either the author or last updater would be suggested.

Good point! I just thought it would be good to remind them in general this really needs updated, so that when they do the next update it could be easily corrected. I'll post to each author as I come across them again. I'm comfortable enough to edit files for my own sites, but not to post code for everyone so I would not want to update them publicly myself.

Angeltown:

Good point! I just thought it would be good to remind them in general this really needs updated, so that when they do the next update it could be easily corrected. I'll post to each author as I come across them again. I'm comfortable enough to edit files for my own sites, but not to post code for everyone so I would not want to update them publicly myself.

It's a public service and one that will only benefit by those that kindly point out improvements. On a related note, though I haven't tried it myself, another has posted that the table type (presumed by me to mean under more recent versions of PHP/mySQL server) is no longer necessary. This is not a claim of fact, but a potential "fix" that if true could make some things a lot easier/cleaner at least until the standard changes again.

Related to the updates of the software, well true there is a little more to it than simply changing a line of code. Going through the actions expected/described in the forum do offer a bit of growth and appreciation to the process. :) but please offer your input where it will provide improvements.