Hi,

  This seems more of a feature request than a bug, per se, so I'll post it here.

  I recently got mojoportal running under the latest version of Mono, but had some difficulties with the included MySQL library, since it doesn't seem to play well with MySQL > 4.0 - apparantly due to the newer encrypted login protocol, but there may be other reasons.  All I got from the exception was that it couldn't connect to any of the servers....

  So, I decided to try the ByteFX library which is included by default with Mono.  It connects to my MySQL 4.1.10 server ok, but I had to use the techniques described here:

                     http://dev.mysql.com/doc/mysql/en/old-client.html

to get around the newer encryption.  After getting some sample code working, I tried to uncomment the ByteFX includes in dbPortal.cs and build a new mojoPortal.Data.dll.  It compiled ok and accepted ByteFX.Data.dll as a reference, but at runtime I got errors about unknown SQL syntax. 

  The problem is that newer MySQL and ByteFX wants "@" as a parameter markers, instead of "?".   So, I  searched and replaced  every instance of "?" with "@", rebuilt again and referenced ByteFX.Data.dll, and everything works ok.

  So then, my request might be obvious by now, I'd like to see dbPortal.cs use a global variable to allow the parameter marker to be configured easily for either library, so instead of hardcode question-marks, it would use something like:

static string P = "@";  // or ?
newMySqlParameter(P + "AllowNewRegistration", MySqlDbType.Int32);
sqlCommand.Append(" " + P + "SiteName , ");

I suppose it'd be kind of a pain to get used to writing new parameters using "P", but it'd sure make it easier to get things working with ByteFX and newer MySQL.

FWIW.




 this will open mojoportal up to a wider audience, imho, since there are a lot of users of MySQL > 4.0 nowadays.

  FWIW.

2/2005 6:26:54 PM

---

>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?

Yup.  I dorked around with the default connector for quite awhile, before deciding to try ByteFX.  I consistently got only the "none of the connections strings worked" message.   I finally wrote up a little test app and compiled first with the default connector, then with ByteFX.  Same message from the default, but ByteFX told me that the encryption was a problem.  After resetting the password for mojo using OLD_PASSWORD() in mysql client, ByteFX connects fine, while the MySQL connector still hangs and eventually reports the same failure.

I tried every permutation on connection string, and even (after reading the thread here about it) tried unix sockets, grasping at straws, since I know the mysqld is listening on TCP.

Perhaps you'll observe the problem when you upgrade to 4.1.x or higher.  I don't know.  It's no problem to fix it for a release, but it makes it challenging to follow your svn version, in any case.

Thanks again for a nice app.  Now if I could just figure out how to change to a new CSS...

Bill