MySQL Driver Auto Entry- best practice

Just for pure curiosity…

Once you start creating a New Server and choose from the Solution Explorer:
>Database Server
>> New Server
>>> MySQL
The following driver caption is entered: org.gjt.mm.mysql.Driver

I have always used: com.mysql.jdbc.NonRegisteringDriver

Is there an actual difference? Which entry is better for Servoy?
org.gjt.mm.mysql.Driver
or
com.mysql.jdbc.NonRegisteringDriver

JC

Hi

You can download the latest version of the jdbc drivers from here:

http://dev.mysql.com/downloads/connector/j/ make sure you get the right driver version for the mySQL version you are using

once you have extracted the files copy/paste the ‘mysql-connector-java-x.x.x-bin’ file into servoy > application_server > drivers folder

When you create the DB connection now you will see a new driver option ‘com.mysql.jdbc.Driver’ use this and I also use a query validation “SELECT 1”

rodneysieb:
When you create the DB connection now you will see a new driver option ‘com.mysql.jdbc.Driver’ use this and I also use a query validation “SELECT 1”

Rodney is correct. That is the same settings I use. The reason for the query validation is because the driver has been known to have a bug where it times out, so the SELECT 1 keeps the connection active.

Yes, I am using the correct drivers for my versions of MySQL (they are in the drivers folder). I just didn’t know which of the the options should have I used (my mistake).

But hey, thanks to this confusing question you provided me with the tip about query validation “SELECT 1” — very cleaver. Yeah, my users have experienced things that now I understand what they were… the times out!

Also, thank you for telling me about the option com.mysql.jdbc.Driver. I never saw it! Actually this is a correction. When I first replied to your posts I haven’t even seen it still.

BTW: I have always used this last option (‘com.mysql.jdbc.NonRegisteringDriver’), and I’ve never had a problem (beside the bug that you guys addressed here). I guess I was lucky.

Thanks a bunch! This issue is RESOLVED!

JC