Hi Kerry,

Our MySql Data layer doesn't use any stored procedures so I'm not sure about any issues creating them from script. We are not setting the delimiter so it uses the default ; 

Changing that would break our installation scripts. I understand from this doc why one would need a different delimiter when running scripts with stored procedures because the procedures have multiple statements in them delimited by ;. But it would be hard to support that in our setup system because it would have to be context aware and know which scripts needed a different delimiter and which would need the default delimiter.

We do use stored procedures in our MS SQL data layer but doing so makes it more work to maintain. I find it much easier to maintain our other data layers because they mostly don't use stored procedures. We've supported use of MySql since way back before they even had stored procedures but once they had them I didn't see any great need to start using them.

To use stored procedures in your custom features MySql data layer you may need to implement your own routine for running the scripts. Probably much easier if you just implement your MySql data layer without them like we do. We have codesmith templates that can generate a lot of the starting code for MySql data layer by pointing the generator scripts at an MS SQL table.

Hope that helps,

Joe