Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MySQL Editions

mysql.com

Post reply on HN
Print view View original

31–40 of 99 posts

Re: MySQL Editions

#31

Post by timhastings »

wlievens wrote: post #30
timhastings wrote: post #28

You have got to admire the evil villany we're up against. Buying the 'M' in LAMP and then exploiting that position. Business first, not the heart and minds of developers. Luckily the 'L' + 'A' + 'P' cannot be bought. LAPP stack anyone?

If you're going the "non-default" route of using postgresql you might as well ditch PHP. Unless P=Python? :-) LAMP is a loaded acronym which these days basically means "a web app built using FOS but not in Java or Ruby".

I am using the LNNMMMMP stack at the moment... Linux, nginx, node.js, memcached, MySQL, Mono, MongoDB and PHP.

Am I normal?

Re: MySQL Editions

#32

Post by anilbioma »

timhastings wrote: post #28

You have got to admire the evil villany we're up against. Buying the 'M' in LAMP and then exploiting that position. Business first, not the heart and minds of developers. Luckily the 'L' + 'A' + 'P' cannot be bought. LAPP stack anyone?

Remove M for MySQL in LAMP and make it M for MongoDB

Re: MySQL Editions

#33

Post by avar »

johnyzee wrote: post #29
candeira wrote: post #26

Earlier quoted context omitted.

How exactly does distributing MySQL as part of your application make your application GPL as well? It's not a retorical question, can you please suggest a case? Unless you outright fork MySQL to make your own database, you can run and distribute it with your proprietary stack without being forced to license your code as GPL. The FSF call it "mere aggregation": http://www.gnu.org/licenses/gpl-faq.html#MereAggregation

Here we go with the amateur legal stuff, but until a more educated comment comes up, as far as I know, it is a question of the drivers being GPL, and coding up against the drivers crosses the threshold.

Not only that, but MySQL AB considered their network protocol to be GPL as well, and went after anyone who tried to make a clean-room implementation of it.

I don't know whether SUN and Oracle still pursue that strategy. Otherwise you could indeed bundle MySQL with some clean-room libraries to talk to the server.

Re: MySQL Editions

#34

Post by rbanffy »

mcs wrote: post #19
plaes wrote: post #13

Earlier quoted context omitted.

Yeah, and also Drizzle, MariaDB and Percona Server.

Drizzle probably is the future of "mysql in the cloud", but it's not quite there yet.

It's certainly not worse than Oracle MySQL...

Re: MySQL Editions

#36

Post by nl »

wlievens wrote: post #30
timhastings wrote: post #28

You have got to admire the evil villany we're up against. Buying the 'M' in LAMP and then exploiting that position. Business first, not the heart and minds of developers. Luckily the 'L' + 'A' + 'P' cannot be bought. LAPP stack anyone?

If you're going the "non-default" route of using postgresql you might as well ditch PHP. Unless P=Python? :-) LAMP is a loaded acronym which these days basically means "a web app built using FOS but not in Java or Ruby".

P always has stood for Perl/PHP/Python (in that order.. it came about back when Perl was more popular than PHP)

Re: MySQL Editions

#37

Post by ax0n »

timhastings wrote: post #31
wlievens wrote: post #30

Earlier quoted context omitted.

If you're going the "non-default" route of using postgresql you might as well ditch PHP. Unless P=Python? :-) LAMP is a loaded acronym which these days basically means "a web app built using FOS but not in Java or Ruby".

I am using the LNNMMMMP stack at the moment... Linux, nginx, node.js, memcached, MySQL, Mono, MongoDB and PHP. Am I normal?

No. You, sir, are not normal. I'd love to know what sort of evil hackery you're cooking with that setup, though.

Re: MySQL Editions

#38

Post by tomjen3 »

jarin wrote: post #12
dangrossman wrote: post #7

Judging by the comments people are confused. The free, GPL edition of MySQL ("MySQL Community Server") is still what you've always had. These are the commercially licensed products. Oracle's shifted around some features and pricing on support plans and such, but if you're not a commercial customer, nothing's changed for you.

What's the difference between community and commercial customers, aside from support? Is InnoDB a feature? Why would MyISAM support be free but InnoDB support have a yearly fee?

InnoDB is basically an ACID storage engine, whereas MyISAM is a storage engine that gives no guarantees about anything.

Re: MySQL Editions

#40

Post by AlexC04 »

RyanGWU82 wrote: post #6
alanh wrote: post #2

Well, fuck. InnoDB is now a premium feature. So long, ACID compliance? Edit “Classic Edition” — what a cop-out name. It should be “Crippled edition.”

Just to be clear, "Classic Edition" is not the free open-source MySQL that we all know and love. It's a separate product for inclusion in other proprietary products. MySQL has always been a dual-license product, and this is similar to previous offerings by MySQL AB and Sun. The "N/A" price probably just means "contact us so our sales team can squeeze you for all you're worth" -- which is how enterprise software deals…

I'm glad I read the comments. I had the same knee-jerk reaction as above. Glad to know I'm still safe :)
Post reply on HN