@Richard Yeah, I know. But what about documentation?
The MySQL code itself is free open source, but Oracle owns the copyright on the MySQL documentation. So as the MariaDB fork adds features, the MySQL documentation becomes more and more inaccurate. At some point there will have to be a full rewrite of the MariaDB docs. Just seems too messy. On Friday, March 8, 2013 8:44:52 AM UTC-5, Richard wrote: > > @Cliff MariaDB!! > > :) > > Richard > > > On Fri, Mar 8, 2013 at 7:36 AM, Cliff Kachinske <cjk...@gmail.com<javascript:> > > wrote: > >> It's not just the legal aspect. >> >> After seeing how poorly Oracle supported OpenOffice, I would be concerned >> about their future support for MySQL as well. >> >> >> On Friday, March 8, 2013 4:43:06 AM UTC-5, Niphlod wrote: >>> >>> This is going nuts. He was fine until now with SQLite, either one of >>> mysql or postgres will do fine, with a total preference on postgres if he >>> doesn't want to employ a legal office to know if he can use mysql or not. >>> >>> PS: the day I'm going to choose mysql over postgres for the combined >>> requirement of having: >>> - a nice syntax to expose an autoincrementing field >>> - is able to accomodate 8M rows with 3 bytes instead of 4 (I'll never >>> consider a tiny or a smallint as an autoincrement-eligible field) >>> it's the day I'll stop working on databases. >>> >>> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "web2py-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to web2py+un...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
