Comentarios en: Is MySQL a toy RDBMS?

Por: fuck america

fuck america — Thu, 02 Apr 2015 11:01:25 +0000

The dictionary definition of monogamy is: married to
only one woman. The constant attention and attendant quasi-celebrity feed and sustain their grandiose
fantasies and inflated self-image. All right maybe I’m using too
a lot credit history here, but most of us
figured we’d enable you to just about all out.

Por: some guy

some guy — Sat, 02 Mar 2013 01:19:52 +0000

Well, the op example is just one of many issues that mysql has. Its optimizer is in fact a TOY. For many reasons. Here is a good example.

Views with group bys arent optimized. The results from the entire view are executed and stored as a temp table before doing any joins. This also applies to derived tables.

Example:
select 1 from smalltable a, ( select * from bigtable b ) where a.id=b.a_id;

If bigtable has a billion rows in it and smalltable has 1 row in it, The entire result from big table must be put into a temp table before it performs the join.

I dont know of any modern rdbms besides mysql that has this issue. All it tells me is that mysql ( as a company, im not blaming just the developers ) didnt take the time or the effort ( or maybe they simply just didnt know how ) to write a real optimizer.

Another example of just piss poor lazyness.

insert into table a ( someintcolumn ) values (»);

This succeeds in mysql and puts a 0 in someintcolumn. Encouraging all the crappy php code to work and making it very difficult to port to any other rdbms. Im not sure if this is just a philosophical thing or a bug. And I dont care. It encourages bugs. I bet half the time php developers dont even realize they have bugs because of things like that. A date with a value of 0000-00-00? Give me a break.

Por: wholesale slippers

wholesale slippers — Wed, 28 Apr 2010 10:16:31 +0000

I searched for something completely different, but found your website! And have to say thanks. Nice read. Will come back.

Por: Jeff

Jeff — Sun, 07 Mar 2010 01:49:43 +0000

Thank you for these comments. I was having the same problem. I have only a few thousand records and it blows chunks even with an index. It seems to not be fetching in the background and returning the first row immediately, like Oracle does when it uses nested loops.

For users who just want to feel like the database is responsive, the first page needs to come back fast, as well as paginate quickly on through. Its counterintuitive for it to be otherwise. The first page of an encyclopedia is just as accessible as the first page of a baby book.

Por: flony

flony — Thu, 29 Oct 2009 21:06:52 +0000

I put my itune info in iphone but I want to remove it. I am afraid if someone just download any expensive application or songs. I want to put itune info only when I want. ________________ unlock iphone

Por: Wave2.org » Blog Archive » PostgreSQL - Rock Solid in the face of forking MySQL

Wed, 03 Jun 2009 21:42:14 +0000

[…] in mass adoption over time, which in turn forced the once web bound database to evolve into a near fully fledged enterprise […]

Por: Mark

Mark — Tue, 14 Apr 2009 19:44:32 +0000

Hi,
I don’t know if I’ll be able to link here, but Shlomi Noach goes into some detail on this issue – and in his case he’s using a WHERE clause to restrict the number of rows, yet the optimizer isn’t using the index as the ORDER BY clause invokes the primary key. So it’s not just the «select *» part which is causing problems.

http://code.openark.org/blog/mysql/7-ways-to-convince-mysql-to-use-the-right-index

Once you’re aware of this as a developer or administrator, you can take relevant action. I’m still happy to use Mysql on my sites; well until most hosts provide PostgreSQL. Having used both Oracle and SQL*Server in the past, I’m well aware that there are gotchas and glitches with all of them. Well, ok, too many on Mysql, but with luck that’ll provide interesting subjects for my blog.

Saludos desde Inglaterra

DBMark

Por: MFR

MFR — Wed, 31 Dec 2008 23:53:11 +0000

Actually, retrieving 1 million record query is already a bad practise to begin with.

Por: Charles

Charles — Tue, 30 Dec 2008 19:47:55 +0000

No, MySQL isn’t a toy… but it’s not a serious tool either. It still can be the right tool for the job, just as long as the people using the tool understand the problems they’ll face.

The optimizer is horrid, and the query planner is a joke. Correlated subqueries, anybody? The most complex query in my employer’s codebase is only so complex because it’s designed to work around how utterly braindead the MySQL query planner is. I’ve even encountered times when FORCE INDEX() won’t actually force the use of that index, if the optimizer thinks that using another index will be faster.

Honestly though, if it wasn’t for the out-of-the-box it-just-works replication, I’d have switched to something else ages ago.

Por: sam pho

sam pho — Tue, 30 Dec 2008 19:46:12 +0000

you’re fired.. go and read the different philosophies of database, and come back and give a write up on something useful like why and what the difference between databases like oracle/postgress and mysql are, and explain why one philosophy differs from the other. Then come back, then maybe the people you work with can slap you around for being a moron.