MySQL database licensing
I have a question about the appliance of the current license Epic Games uses in regard to third party products. To sum it up, basically it's illegal to use third party products like MySQL unless you pay for a license (which could cost a handsome couple thousands of dollars). Is it also illegal to use a workaround for this? For example, am I allowed to make cURL calls to a webserver, which in turn is connected to a MySQL database? Or am I allowed to use alternative solutions to MySQL like MariaDB, PostgreSQL, or SQLite? If not, it would be a bit rough on start-ups to get a system like that going unless they have a solid invester willing to pay for licensing costs.
Using PostrgreSQL/unreal-sqlite3 is the safer and more conservative approach, and both are fine to use with UE.
MySQL, without the commercial license, may be OK, depending on the nature of the use, but its a fact-specific question without a clear answer.
In response to your final question, the MIT license is OK for use with UE, as are the BSD License, Microsoft Public License, and the Apache License. These licenses are expressly called out as permitted under Section 1(b)(ii) of the EULA.
answered Apr 04 '17 at 03:51 PM
DudleyStephens ♦♦ STAFF
These answers are incorrect regarding the use of MySQL in the manner that you have described in your question.
I'm not a lawyer so do not take this answer as solid legal advice, but generally speaking:
Keep in mind that there are separate licenses for both the MySQL database engine itself and for the various connectors used to communicate with it directly.
My understanding of the usage you describe in your question is that you mean the client would be calling to a web server that you do not distribute to clients as part of your game. If you are using MySQL in that manner, you would not be redistributing MySQL or its connectors to users so licensing is not a concern for you in that aspect. The GPL license only affects code that you distribute to other parties. Internal usage within an organization is totally free and not subject to any conditions. There is no such thing as 'internal distribution' that would restrict the usage of your code by requiring it to be GPLed.
Connecting to a remote service that runs MySQL (or MariaDB or any other GPL software) in the background is also free.
For internal programs for which you own all the copyright(s), there is essentially no risk in using GPL software. The argument you can use in your defense is that if the software became GPL as part of the distribution, you as the copyright holder could immediately revert your part back to its original copyright. No one has the right to require you to reveal or redistribute your code to the outside of your organization even if you would have distributed it internally linked with GPL software!
The above is an excerpt from MariaDB's creator (who is also the creator of MySQL) and he is the one who chose GPL licensing for MySQL) so while he may not be a lawyer either, I would assume he knows a thing or two about the licensing and its implications ;)
For full reference please see the following page this information was drawn from by visiting this link
Follow this question
Once you sign in you will be able to subscribe for any updates here