Why would a non-expert on a topic write an whitepaper about it? Makes no sense...
Sorry for being so picky, but I'm just a bit fed up with that kind of nonsense.
Regardless of the intent, the result is malicious as such FUD on the net hangs around and is copied and quoted. Wouldn't you rather compete by focusing purely on the positive points that your own offering provides?
Anyway, your image is yours to build or undermine. It's a choice.
Space from deleted rows and old versions are automatically reused, no explicit maintenance is required for this. I don't know what that person was referring to; if he/she has a valid point, I'm sure they can be more specific about the matter.
Sorry, but you're just plain wrong. MVCC is a fudamental design feature in InnoDB, and so it has been present in MySQL for over 4 years now. There's just no excuse.
Facts need a source, you don't just make them up;-)
Indeed there used to be an issue with many-table joins. Has been resolved in MySQL 5.0 with a greedy optimization algorithm.
By the way, MySQL's optimizer is way less trivial than you may think. Don't believe everything other people tell you;-) But heck, you could even look at the code yourself and find out....
Re the whitepaper you refer to, it contains quite a few factual errors, including the fib about MySQL not having any MVCC storage engine. Such mistakes reflect rather badly on the expertise of the whitepaper authors. Can't be good for business....
It is so much better to compete on positive aspects of ones own product, rather than spread FUD about another. It makes one wonder.
Where will you go, what will you do? Ah, but wait! The article gives a pointer there, too... Oracle. They don't want to support users on that platform. So, go for it. This could be your ultimate "put your money where...."
Darn pity it's not open source. Hmm actually, that gives you another option also: you could go for Microsoft.
According to Monty, the correct answer for MySQL Version 1.0 is 23rd May 1995.
Two people got really close, 20th and 26th May, so they will each get an anniversary mug and other stuff.
The person who rambled on about Nostradamus amazingly got close as well (May 28th) and I reckon that in any case such creativity deserves to be rewarded;-)
Those who assumed that there was any significance in when I first put the mugs online... sorry. The mugs just appeared when Mike Zinner finished the design.... At the time, I did not even know the precise date. We had to ask Monty later.
Thanks to everybody for their participation and good humour.
Regards, Arjen. Community Relations Manager, MySQL AB
This response is so wacko, I reckon it deserves a prize. It is -amazingly- not even very far off. The exact date, according to Monty, was May 23rd. So, congratulations on that;-)
Please email me (arjen [at] mysql [dot] com) with your name/address details, and I'll make sure you get a mug!
Note that as your email is not public on slashdot, it's upto to prove that you are you.
Regards, Arjen. Community Relations Manager, MySQL AB
Thank you for making these sensible points. I really think way too much time is spent on bagging other people's choices.
Why would we want to give proprietary vendors ammo like "the open source world is divided"... why not spend time on promoting the various open source solutions in general, and presenting the diversity and choice that it offers as the good thing that it is?
> Until that day however, stored procedures are "useless" and "needlessly complex." The same with views and cursors. > [...] > Our golden calf does not yet support them in production and until it does they are obviously useless bloat. > Do you like it? I call this piece "Ode to a MySQL Fanboy."
Years old joke recycled again, shame on you. And it's still scored funny. THAT is funny.
But seriously, if you see any such statements in the present-day world, please do let me know, then we can do something about it. Thanks!
Slashdot Mirror
OurDelta has most accurately been described as a "distro for MySQL", just like Red Hat and Ubuntu are distros of Linux.
mysql> insert into dat values ('9999-99-99');
ERROR 1292 (22007): Incorrect date value: '9999-99-99' for column 'd' at row 1
Oracle didn't buy MySQL, you silly.
Why would a non-expert on a topic write an whitepaper about it? Makes no sense... Sorry for being so picky, but I'm just a bit fed up with that kind of nonsense. Regardless of the intent, the result is malicious as such FUD on the net hangs around and is copied and quoted. Wouldn't you rather compete by focusing purely on the positive points that your own offering provides? Anyway, your image is yours to build or undermine. It's a choice. Space from deleted rows and old versions are automatically reused, no explicit maintenance is required for this. I don't know what that person was referring to; if he/she has a valid point, I'm sure they can be more specific about the matter.
Sorry, but you're just plain wrong. MVCC is a fudamental design feature in InnoDB, and so it has been present in MySQL for over 4 years now. There's just no excuse. Facts need a source, you don't just make them up ;-)
Indeed there used to be an issue with many-table joins. Has been resolved in MySQL 5.0 with a greedy optimization algorithm.
;-) But heck, you could even look at the code yourself and find out....
By the way, MySQL's optimizer is way less trivial than you may think. Don't believe everything other people tell you
MySQL 5.0 can warn or reject on such instances.
Re the whitepaper you refer to, it contains quite a few factual errors, including the fib about MySQL not having any MVCC storage engine. Such mistakes reflect rather badly on the expertise of the whitepaper authors. Can't be good for business....
It is so much better to compete on positive aspects of ones own product, rather than spread FUD about another. It makes one wonder.
As Brian Aker wrote weeks ago, MySQL 5.0 can be strict about those things.
Which is good.
Oh, look: http://www.eweek.com/article2/0,1895,1846635,00.as p
...."
SCO also partners with EnterpriseDB (PostgreSQL), Borland (InterBase), Computer Associates (Ingres), IBM (Informix).
Where will you go, what will you do? Ah, but wait! The article gives a pointer there, too... Oracle. They don't want to support users on that platform. So, go for it. This could be your ultimate "put your money where
Darn pity it's not open source. Hmm actually, that gives you another option also: you could go for Microsoft.
Hi everybody,
;-)
According to Monty, the correct answer for MySQL Version 1.0 is 23rd May 1995.
Two people got really close, 20th and 26th May, so they will each get an anniversary mug and other stuff.
The person who rambled on about Nostradamus amazingly got close as well (May 28th) and I reckon that in any case such creativity deserves to be rewarded
Those who assumed that there was any significance in when I first put the mugs online... sorry. The mugs just appeared when Mike Zinner finished the design.... At the time, I did not even know the precise date. We had to ask Monty later.
Thanks to everybody for their participation and good humour.
Regards, Arjen.
Community Relations Manager, MySQL AB
Congrats!
The exact date, according to Monty, was May 23rd.
So you were pretty close.
Please email me (arjen [at] mysql [dot] com) with your name/address details, and I'll make sure you get a mug and other stuff I can find.
Note that as your email is not public on slashdot, it's upto to prove that you are you.
Regards, Arjen.
Community Relations Manager, MySQL AB
Congrats! You were pretty close.
The exact date, according to Monty, was May 23rd.
Please email me (arjen [at] mysql [dot] com) with your name/address details, and I'll make sure you get a mug and other stuff I can find.
Note that as your email is not public on slashdot, it's upto to prove that you are you.
Regards, Arjen.
Community Relations Manager, MySQL AB
This response is so wacko, I reckon it deserves a prize. ;-)
It is -amazingly- not even very far off.
The exact date, according to Monty, was May 23rd.
So, congratulations on that
Please email me (arjen [at] mysql [dot] com) with your name/address details, and I'll make sure you get a mug!
Note that as your email is not public on slashdot, it's upto to prove that you are you.
Regards, Arjen.
Community Relations Manager, MySQL AB
Thanks for your feedback. A strict mode is actually being implemented.
Thank you for making these sensible points.
I really think way too much time is spent on bagging other people's choices.
Why would we want to give proprietary vendors ammo like "the open source world is divided"... why not spend time on promoting the various open source solutions in general, and presenting the diversity and choice that it offers as the good thing that it is?
> Until that day however, stored procedures are "useless" and "needlessly complex." The same with views and cursors.
> [...]
> Our golden calf does not yet support them in production and until it does they are obviously useless bloat.
> Do you like it? I call this piece "Ode to a MySQL Fanboy."
Years old joke recycled again, shame on you.
And it's still scored funny. THAT is funny.
But seriously, if you see any such statements in the present-day world, please do let me know, then we can do something about it.
Thanks!