![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am developing an application for a client where the community edition works fine and am wondering what benefit there would be to upgrade to a paid version. |
#3
| |||
| |||
|
|
Joe Hesse wrote on 23.12.2010 22:19: I am developing an application for a client where the community edition works fine and am wondering what benefit there would be to upgrade to a paid version. If you distribute your application with MySQL (and your application is closed source) then you need to pay for a license because of the GPL license. If you distribute your application _without_ MySQL I'm not sure if you need to pay for a license or not. But if your application *only* works with MySQL, then I think(!) this falls under derivative work and requires a commercial license as well (again assuming your application is non-GPL) Regards Thomas |
#4
| |||
| |||
|
|
Hi, The MySQL community edition is the no cost GPL version, the MySQL standard edition is the lowest cost ($2,000) of the paid versions. Please point me to some documentation showing the differences between the two. |
#5
| |||
| |||
|
|
The MySQL community edition is the no cost GPL version, the MySQL standard edition is the lowest cost ($2,000) of the paid versions. Please point me to some documentation showing the differences between the two. |
|
I am developing an application for a client where the community edition works fine and am wondering what benefit there would be to upgrade to a paid version. |
![]() |
| Thread Tools | |
| Display Modes | |
| |