I have to admit I prefer to use and heavily promote PostgreSQL myself but some clients are forced into using MySQL because of other systems that are MySQL only.
Now MySQL 5 is out is anyone using version 5 with Servoy yet?
Any experiences?
We switched the application we are developing from Sybase ASA to MySql 5.0 a couple of months ago. So far we are happy…
Would you be able to share with us the rationale behind switching from SQL Anywhere to MS SQL? For those of us who are relatively new to the world of SQL, the variety of choices for the back end is a bit daunting and one could spend the next year learning about the differences between them before one is even remotely qualified to make choices and recommendations.
I really like the mobility/offline possibilities presented by ASA, plus the fact that ASA Server & Client are included with Servoy licenses. (And I think there is real business potential in building a relationship with Sybase VARs and account managers, and also I hope that the partnership between Servoy and Sybase remains strong). Yet I notice that not many Servoy developers seem to use iAnywhere products nor recommend them to clients. Of course, if a different back end is already in place, one would wish to leverage existing licenses. But when the choice-point arises for choosing a back end, I always wonder what considerations go into that choice. I would love to see some kind of chart that points up the pro’s and con’s of various SQL environments (and maybe in a few years I’ll know enough to create such an animal myself, but for now am not qualified!).
So, for starters … what was behind the move to MS SQL from Sybase’s SQL Anywhere? If you are at liberty to say, of course. Thanks in advance …
kazar
We liked all of the functionality of ASA fine but we mainly switched to MySql 5.0 (once they came out with stored procedures, relationships and triggers) because the array of other third-party tools that we might want to use against the same DB was infinately greater with MySql. Also, the no license fees is an added bonus.
Thanks for the good answer … and I’m sorry for my misreading of which db you have selected … my brain had translated “MySQL 5” into “MS SQL 2005” (recently released).
I must confess that the licenses for MySQL, which I’ve read from end to end, still have me confused. It really doesn’t seem free, unless you are willing to submit whatever you create with it back to the Open Source community (which I certainly cannot do with my clients’ applications).
But certainly the prevalence of MySQL is indisputable. I know it is the only db made available by Datatude’s domain hosting provider, unless one rents a virtual private server or collocates a server and installs something different.
Thanks again,
kazar
The license to USE mysql as you got it is totally free. You can create whatever applications you want and you can copywrite what you create.
If you MODIFY the mysql ENGINE then you must share those enhancements to mysql itself back with the community.
I think this is wrong.
If you develop a commercial application based on MySQL you have to buy a license.
Yup, when you use mysql in a commercial environment the database is not free.
a.mariottini:
I think this is wrong.
If you develop a commercial application based on MySQL you have to buy a license.
It seems very clear from the MySQL web site that this is correct.
The Commercial License, which allows you to provide commercial software licenses to your customers or distribute MySQL-based applications. This is for organizations that do not want to release the source code for their applications as open source / free software; in other words they do not want to comply with the GNU General Public License (GPL). For more detail on the Commercial non-GPL License, click here. Or, if you want more information on pricing, click here.
For those developing open source applications, the Open Source License allows you to offer your software under an open source / free software license to all who wish to use, modify, and distribute it freely. The Open Source License allows you to use the software at no charge under the condition that if you use MySQL in an application you redistribute, the complete source code for your application must be available and freely redistributable under reasonable conditions. MySQL AB bases its interpretation of the GPL on the Free Software Foundation’s Frequently Asked Questions. For more information on MySQL’s Open Source License, click here.
At MySQL AB, we believe in open source / free software and we welcome all initiatives to publish more software under the GPL license, just as we have done.
In their simplest form, the following are general licensing guidelines:
- If your software is licensed under either the GPL-compatible Free Software License as defined by the Free Software Foundation or approved by OSI, then use our GPL licensed version.
- If you distribute a proprietary application in any way, and you are not licensing and distributing your source code under GPL, you need to purchase a commercial license of MySQL
- If you are unsure, we recommend that you buy our cost effective commercial licenses. That is the safest solution. Licensing questions can submitted online for our advice, and we encourage you to refer to the Free Software Foundation or a lawyer as appropriate.
I don’t see any ambuguity in the above (quoted from http://www.mysql.com/company/legal/licensing/), yet most of the world (gstein is not alone on this point!) seems to think MySQL can be used for free without restriction.
Now, there may be some OS’s and/or specific brands of computers that include at least the server license for MySQL. OS X Server comes to mind, though I am unclear on the allowable # of connections.
postgreSQL, on the other hand, is totally free (donations gladly accepted).
kazar
For an interesting view of mySQL vs PostgreSQL, take a look at
I wonder if Servoy could look into this and tell us if solutions built on MySQL need an additional MySQL license in order to take it commercial. It appears that web solutions that access MySQL don’t require the license, because you are not actually distributing MySQL. I wonder if Servoy is the same? If your client is simply accessing the database remotely, I wouldn’t think you would have to have a MySQL license.
-Anthony
ROCLASI:
I have to admit I prefer to use and heavily promote PostgreSQL myself but some clients are forced into using MySQL because of other systems that are MySQL only.
Now MySQL 5 is out is anyone using version 5 with Servoy yet?
Any experiences?
Switched from MySQL 4.1 to MySQL 5.0.
Everything is working perfectly but I still haven’t had the chance to try stored procedures, triggers and functions.
Anyway I reccomend MySQL 5 for any new MySQL installation.
Only remark: use query validation (‘select 1;’ is ok) in your Servoy DB Server config otherwise you’ll experience some annoying timeout errors in servoy log. This applies to 4.1. also, look for an old post of mine for details.
I’m writing a short tutorial on using MySQL with Servoy but I can’t find the time to finish it…
If you need further info feel free to ask.
Please note that the software is free to use for those who never copy/modify/distribute it (and I happen to know that gstein fits in this category):
Free use for those who never copy, modify or distribute. As long as you never distribute the MySQL Software in any way, you are free to use it for powering your application, irrespective of whether your application is under GPL license or not.
If I may interject my own vague stereotype: I believe most people who see it as free are using it without redistribution/modification.