Comments on: More MySQL Idiocities http://blog.charcoalphile.com/2007/10/28/more-mysql-idiocities/ On Databases, Recovery, Tech Mon, 06 Sep 2010 10:41:42 +0000 http://wordpress.org/?v=2.2.1 By: admin http://blog.charcoalphile.com/2007/10/28/more-mysql-idiocities/#comment-169 admin Mon, 10 Mar 2008 22:30:59 +0000 http://blog.charcoalphile.com/2007/10/28/more-mysql-idiocities/#comment-169 Thanks for the workaround. Unfortunately, it's too late for MySQL. After running into stuff like this over and over again while working on a series of small MySQL projects, I refuse to use it again. Basically what it comes down to is this: - MyISAM sucks, but it's fast. - InnoDB is slower at some things, but it supports transactions and many other features I use all the time. However, it still suffers from most of the quirks that MyISAM does, and transactions don't always work like they should (try BEGIN; CREATE TABLE; ROLLBACK; ...). - Falcon is slow as hell from all of the benchmarks I've seen so far... I haven't actually tested it. - Maria? What the hell is this! Why do they always create new engines to "fix" the things that are "broken" in the previous one!? Thanks for the workaround. Unfortunately, it’s too late for MySQL. After running into stuff like this over and over again while working on a series of small MySQL projects, I refuse to use it again.

Basically what it comes down to is this:

- MyISAM sucks, but it’s fast.
- InnoDB is slower at some things, but it supports transactions and many other features I use all the time. However, it still suffers from most of the quirks that MyISAM does, and transactions don’t always work like they should (try BEGIN; CREATE TABLE; ROLLBACK; …).
- Falcon is slow as hell from all of the benchmarks I’ve seen so far… I haven’t actually tested it.
- Maria? What the hell is this! Why do they always create new engines to “fix” the things that are “broken” in the previous one!?

]]> By: Ian eure http://blog.charcoalphile.com/2007/10/28/more-mysql-idiocities/#comment-161 Ian eure Fri, 07 Mar 2008 21:23:09 +0000 http://blog.charcoalphile.com/2007/10/28/more-mysql-idiocities/#comment-161 Yup, I've been bitten by that before, too. Here's the workaround: mysqldump db | sed s/' DEFINER=`.*`'// > db.mysql i.e. it strips out the DEFINER from the CREATE VIEW statement, so when you load the dump, the owner is set to the user you load it as. Yup, I’ve been bitten by that before, too.

Here’s the workaround:

mysqldump db | sed s/’ DEFINER=`.*`’// > db.mysql

i.e. it strips out the DEFINER from the CREATE VIEW statement, so when you load the dump, the owner is set to the user you load it as.

]]>