Im using LLBLgen to generate code for mysql. Currently im using Corelabs mysql provider. However due to the lack of good support from Corelab and some bugs i have found in their software when running some web stress tests i would like to do my own implementation to the MySQL Connector/Net provider.

Can you provide some help or describe the steps involved in order to get my own custom mysql provider?

As a customer you've access to the drivers sourcecode in the SDK and the DQE sourcecode in the runtimelibs.

So a good place to start is to pick the MySql code in there and port it to use the MySql GPL-ed provider.

be aware that that provider is GPL-ed. If you distribute the modified DQE dll with your app to use the mysql provider of mysql itself, you have to buy a license from them, or distribute the code of the DQE, but you are not the copyright holder of that code so you are not entitled to do that. That's also the mess we tried to avoid so why we picked corelab's stuff. We aren't happy with corelab's code either, but there's little choice.

I know I am bumping a very old post, but I had a question for you (Otis).

If I understand correctly, we would have to purchase a license from MySQL in order for you to use the MySQL connector driver with LLBLGEN. It seems work-able? Can you structure it so the MySQL connector support is an "add-on" to LLBLGEN so only your customers that require such support will have to pay the MySQL license fee? As it is now, we have to pay a Corelabs license fee anyway right?

Perhaps there is more to the problem than I understand.

It just would be nice to have the MySQL work based on the MySQL supported driver library (unless the Corelabs work is superior).

Otis wrote:

As a customer you've access to the drivers sourcecode in the SDK and the DQE sourcecode in the runtimelibs.

So a good place to start is to pick the MySql code in there and port it to use the MySql GPL-ed provider.

be aware that that provider is GPL-ed. If you distribute the modified DQE dll with your app to use the mysql provider of mysql itself, you have to buy a license from them, or distribute the code of the DQE, but you are not the copyright holder of that code so you are not entitled to do that. That's also the mess we tried to avoid so why we picked corelab's stuff. We aren't happy with corelab's code either, but there's little choice.

rracer99 wrote:

I know I am bumping a very old post, but I had a question for you (Otis).

If I understand correctly, we would have to purchase a license from MySQL in order for you to use the MySQL connector driver with LLBLGEN. It seems work-able? Can you structure it so the MySQL connector support is an "add-on" to LLBLGEN so only your customers that require such support will have to pay the MySQL license fee? As it is now, we have to pay a Corelabs license fee anyway right? Perhaps there is more to the problem than I understand.

MySql SA has a mysql connector, it's GPL-ed so if you want to use it for anything serious and not open up your own code, you need to use a non-GPL-ed version. This non-GPL-ed version is at least 250 euro/developer.

Corelab (devart nowadays) also provides a mysql connector. It's much less expensive than the Mysql SA one.

If you want to use llblgen with mysql, you need to use the connector we currently support, which is the corelab one. As corelab changed its name to devart and with that also the assembly names, we have a bit of a problem at the moment because users who want to purchase the mysql connector from devart, will get one which isn't recognized by our driver, as it's called 'DevArt....' instead of 'CoreLab...'. We have code in test at the moment which should solve this properly so we expect a solution soon.

So if you don't use mysql, you don't need to buy anything.

It just would be nice to have the MySQL work based on the MySQL supported driver library (unless the Corelabs work is superior).

They both aren't that great, corelab's 'works' but its protection system has plagued us for a long time, and if I can kick them out, I would. However Mysql SA has been a royal pain in the *** for a long time as well, as they refuse to properly answer my questions regarding licensing, and only want us to become a MySql reseller which we refuse to become as we have no business with mysql nor do we want to resell their stuff.

It's a bit of a pain, I admit, and if I could solve it properly, I would. For v2.6 we aren't planning to give out another driver for MySql SA's connector (the GPL-ed one), for v3.0 we are planning to, as the 3.0 code is more suitable to do this.

So in short: For using MySql databases with v2.6 you therefore need to have the corelab connector, v4.x or lower. DevArt's connectors won't work. I'm not sure if devart still sells v4.x connectors. We hope to have a fix for this soon so you can use corelab or devart's connectors with llblgen v2.6.

In v3 is there an option to use the MySQL Connector/Net driver or is the corelab or devart driver still required?

Still required for MySql: CoreLab's MySqlDirect.NET provider for .NET 2.0 or higher, or DevArt's MySqlDirect.NET provider v5.x or higher.

Couldn't find "MySqlDirect.NET" on DevArt. Is this the correct one?

http://www.devart.com/dotconnect/mysql/editions.html

What is the minimum edition required?

Yes.

From the looks of that list, the Express would do fine (which is free), if you're going to use our ORM framework. If you're going to use EF, you need the professional version.