Re: Is difference between PostgreSQL and mySQL licences for client application minor only

In the last exciting episode, "Andrus" <eetasoft(at)online(dot)ee> wrote:
> I created closed source Postgres/mySQL client application.
>
> When using PostgreSQL as backend I can include Postgres server
> binary code in my application distro.
>
> When using mySQL my application setup can load mySQL server
> installation package from mysql website and execute it
> automatically.
>
> This minor difference is the only difference between Postgres/mySQL
> licenses in client application, right ?

That doesn't sound consistent with the arrangements that MySQL AB
expect for commercial users of their products.

They indicate assortedly that:

- If you are developing and distributing open source applications
under the GPL, or some OSI-approved license, you are free to use
MySQL(tm) "for free."

- If you are *not* licensing and distributing your source code under
the GPL, then MySQL AB expects you to use their "OEM Commercial
License," which involves negotiating a contract with their
sales team.

Your scenario seems to clearly fall into the scenario where MySQL AB
expects you to pay them license fees.

If you don't include MySQL(tm) with your product, then that presumably
imposes the obligation to pay MySQL AB a license fee on the purchasor
that does the download. That may leave your hands clean, but if you
do not warn your customers of their obligation, and legal problems
arise, they may not be too happy with you...
--
(format nil "~S(at)~S" "cbbrowne" "cbbrowne.com")
http://linuxdatabases.info/info/lsf.html
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \