Re: Support recent ByteFX and MySQL > 4.0
Actually, I was using ByteFX in previous releases of mojoportal and switched to the newer MySQL Connector for .NET because users with certain versions of MySQL 4.1 were complaining that the ByteFX driver did not work for them. The newer MySQL Connector for .NET needs the ? while the ByteFX needs the @, that part has nothing to do with which version of MySQL.
It sounds to me like you are reporting just the opposite of what others are saying and that the ByteFX worked for you where MySQL Connector did not? That is very surprising since the MySQL Connector included in the most recent version of mojoportal is the newer driver. ByteFX is never going to have any enhancements or bug fixes as the author Reggie Burnett now works for MySQL and also wrote the newer MySQL Connector.
I have actually been considering going back to the ByteFX driver due to licensing issues with the newer MySQL Connector.
I am currently running MySQL 4.0.23. I will have to upgrade sometime soon and experiment myself before making a decision. My main reason for upgrading from ByteFX to the newer MySQL Connector was because I was told that the ByteFX driver did not work with MySQL 4.1 and newer whereas the MySQL Connector did.
To me it sounds like
solved the problem for ByteFX but required using the older security model
But the newer MySQL Connector is supposed to work with newer versions of MySQL even including version 5 so I would assume it does support the newer security model. I'm thinking that perhaps the newer security model requires a different syntax in the connection string and that may have been the original problem you were having. Or perhaps the same fix for ByteFX would have made the Connector work.