Slashdot Mirror
MySQL AB Settles With NuSphere
PCM2 writes "It appears that MySQL AB has settled its dispute with NuSphere over use of the MySQL trademarks. CEO Marten Mickos has punctuated the occasion with a donation to the FSF -- but there's no mention of what the actual terms of the settlement were, and there's no statement on NuSphere's site either (yet)."
As long as I don't have to start calling it GNU/MySQL I will be satisfied.
What has not been settled is the debate over the pronounciation of SQL.
If you get an error, type "OVERRIDE" or "SECURITY OVERRIDE" and then try the optimize command again.
MySQL AB is pleased to announce that it has settled its lawsuit with Progress Software Corporation and NuSphere Corporation. For more information, see the joint press release at
http://www.mysql.com/press/release_2002_14.html
Regards, Monty
How is it that one careless match can start a forest fire, but it takes a whole box to start a campfire?
ess queue el
With OS X came a bundling of MySQL, and CTOs (Chief Technology Officers) across the country thought to themselves that "Hey, if a big profitable company puts this package of OpenSource software into their flagship OS, it must be OK to use. Let's stop dishing out tens of thousands of dollars a year to Oracle and let's just use this free RDBMS implementation." (Sure, PostreSQL is a bit more weathered, but both are pretty nice considering their price).
Wider acceptance of MySQL and its related products/technologies is a good thing, and solving this NuSphere trademark violation is only a good thing in my mind.
If you celebrate Xmas, befriend me (538
-SheWhoWalksWithToesLikeCobras Please enter any 11-digit prime number to continue...
I'm glad they both had the sense to overcome this legal dispute. M$ was probably ready for this to fall through and use it as a marketing technique for their SQL server. Whoops!
"This food is problematic."
Can someone post a BRIEF summary of what the lawsuit was about? I can't tell from the annoucement what the issues were that were resolved.
We are very glad it is over now. Thanks to all of you (and there were many of you) who supported us through this process. You are doing a great job defending free software and open source principles.
Marten Mickos, MySQL AB
I didn't know much every single detail regarding this whole argument until I read this page of frequently asked question on the MySQL vs. NuSphere dispute.
It talks about who actually created the software, as well as their take on others' claims that MySQL AB attempted to "change rules in mid-agreement" with NuSphere.
If you celebrate Xmas, befriend me (538
Pleased to see the settlement. I've made extensive use of Nusphere's mysql-related product line and PHPEd. Excellent products in a nicely bundled form. BTW, I think Nusphere has some of the best mySQL training around.
"When I grow up, I'll be stable."
MySQL on the other hand is much more open. Maybe that's because they are faster in most situations, or maybe it's because they really do have a better philosophy.
If you look at what happened between MySQL and NuSphere, MySQL was never out to crucify anyone. They don't verbally bash anyone or toot their own horn. Look at what they say on their website about their own benchmarks and how they repeatedly point out that the competing products they have tested were not completely optimized due to their lack of knowledge regarding optimizations for those products.
I think MySQL will eventually be the dominant database for two reasons:
- It's easier/faster
- It cots a lot less than Oracle
And to top it all off, they are a company that we can feel good about supporting. I have a feeling that if they were to become as large as MS, they would never try anything dirty to gain greater market share or to hold on to what they already have. I think a few other companies could do well to learn by the example MySQL has given us. You don't have to play dirty to get ahead.How is it that one careless match can start a forest fire, but it takes a whole box to start a campfire?
Aargh ... how will it take until we start the "but is MySQL really an RDBMS" thread here?
... there, I've just done it!
(don't click here!)
(or here!)
Oops, wait
Now I can rest easy, knowing that they're are no more worries about those companies destroying each other. None of my mySQL installations are in danger. I'm off to celebrate!
Writers imply. Readers infer.
I use MySQL and Oracle 8i and 9i in my professional and personal lives, and while MySQL is very useful for quick 'n' easy databases, it is not something I would want to build a real-life large application around, for the simple reason that it is SO nice to be able to embed a nice set of business rules right in the database. That, for me, gives Oracle the edge currently. And yes, MySQL will, I have no doubt, grow these features essential for large and complex applications. And guess what? It will get slower/harder as it does so, and I also believe it will get more expensive.
Call me old fashioned, but I like a dump to be as memorable as it is devastating - Bender
what
The Raven
The Raven
Use it for lighter noncritical work? Quite possibly.
Transactions, stored procedures, and triggers are not just 'bells and whistles' to large database applications. They are core features. You can't easily port from a system that has them to one that does not.
What was the end result?
As long as that fat bearded monster, RMS, doesn't GPL (General Poverty License)it , you'll never have to prefix GNU before MySql.
...and there was me thinking I'd cleared that up in my last Slashdot post.
In summary: either S - Q - L or "sequel", interchangeably. Or "squirrel" if you're a freak [grin]
Cheers,
One advantage of the Berkeley license is that it has been tested in court and ruled valid. And it doesn't have the most dicey quality of the GPL: its viral nature.
Unfortunately you would be incorrect.
Sequel was a predessor to SQL.
They are not they same thing. Though they are used interchangably (mainly by DBAs)
and use a database written by people who didn't spend years denying that these features were useful, much less desirable...
Actually in swedish MySQL can be pronounced "myskul" (not at all pronounced like "my skull" by the way...) wich means something like "cozy fun"
Isn't that fun... and cozy.
In these cases, PostgreSQL is probably a viable candidate. It has much better SQL support, triggers, support for stored procedures in multiple language types, and a MVCC locking system that even Oracle doesn't match.
The 7.x series is pretty stable, and you can now vacuum without shutting down.
That being said, MySQL is just a lot easier to work with, especially wrt modifying table structure, support tools, and access control. And having built in braindead replication is nice too.
PostgreSQL's got MVCC, which is miles ahead.
Subselects are currently in development for 4.1.
Check. PostgreSQL's got that one, too.
Stored procedures are planned for 5.0.
Check.
They are looking at triggers.
Duh, that one too.
And the speed is pretty much on par with MySQL. And it's so easy to setup, if you haven't tried it for some time, do so now, it's really stable, fast and loaded with goodies!
What is it about Postgres that it keeps being ignored compared to MySQL? Perhaps MySQL is used by more people because it targets slightly smaller applications? Thus you hear it mentioned more?
Or, perhaps the hard-to-remember name. Sounds like a fertilizer brand, to be frank.
Table-ized A.I.
as long as the US President is pronouncing "nuclear" as "nucular", the correct pronounciation of SQL is not all that important.
The court may find that the terms of the GPL licence has been upheld, even though it's done in such a way as to make it completely unusable for anyone else to work on.
I can't really say how a lawyer could twist the GPL, but there's a few sections there where I'm sure they would:
"reasonably considered independent and separate works" and "part of a whole" and "mere aggregation". Does for instance two separate installers, one for the GPL part, one for the rest go as "parts of a whole" or "separate works"? Or various wrappers / OS communications interfaces (COM etc.)? Or something like "preferred form of the work for making modifications to it". Oh sure, we prefer to make our modifications in assembler, right? Or "major components of the operating system" Why, IE, WMP and whatever are components of Windows, right?
I'm not saying any of these parts *are* broken. But they don't hold much confidence until clearly defined by a court of law.
I agree, a defendant would never try to bust the GPL, but he *could* break the results that the GPL tries to achieve. And that, would actually be a far worse result as it would put all GPL-licenced programs in the same situation.
Kjella
Live today, because you never know what tomorrow brings
without the gui development.It has sql,it stores each table as its own file and has transactions that really dont use a transaction log, which means if something goes wrong during a commmit you still get half commited data.
if mysql wasnt the guiless version of FOXPRO.
I pronounce it 'them words', being as I am from the North of England
;)
(that's the old England in the Yoo Kay, for those of you who's forefathers (and mothers) came from over here).
As in 'Make a statement using them words and bung it in the database'.
--Jargon for Jerx
(yet to be published - probably never)
Well, if you look in the WHOIS database, part of the settlement is listed there. Looks like MySQL AB now owns the domain mysql.org and not NuSphere anymore.
"It was the first time that the GPL, the cornerstone of the open source and free software movements, had been dragged before the bar. [...]
In the process, a federal judge deemed the GPL enforceable and binding."
... Any resemblance between the above views and those of my employer,
my terminal, or the view out my window are purely coincidental. Any
resemblance between the above and my own views is non-deterministic. The
question of the existence of views in the absence of anyone to hold them
is left as an exercise for the reader. The question of the existence of
the reader is left as an exercise for the second god coefficient. (A
discussion of non-orthogonal, non-integral polytheism is beyond the scope
of this article.)
- this post brought to you by the Automated Last Post Generator...