InnoDB and MyISAM in 2019 ....

#native_company# #native_desc#

#native_cta#

This site is best viewed in a modern browser with JavaScript enabled.

InnoDB and MyISAM in 2019 ....

dalecosp

Well, InnoDB has been the default in MySQL for quite some time now ...

I still have some legacy tables in MyISAM. Is there any practical reason I should NOT move them towards InnoDB?

How about any esoteric ones?

Weedpacket

Hmmm... the silence suggests "no" If I recall, the only advertised advantage MyISAM had over anything more ACID-compliant was in retrieval speed—is that still relevant these days?

Even if disk access speeds haven't improved and in a read-only scenario it still has a distinct edge in access speed, throwing enough RAM at the server would give the relevant files a chance to be cached in core, so the difference would be a lot less.

dalecosp

Well, in my mind, speed is always relevant.

As for RAM, from a recent email:

VP_of_IT wrote:
If finances were ‘normal’ I would not worry about adding RAM.

So ... there's that.

I'll need to go back and see if I did actually change this. I think I was considering doing this so I could use LIMIT on an INNER JOIN? ... but I can't remember for sure (just back off a 5-day weekend and the point behind this doesn't seem to be in any recent documentation ...)

Weedpacket

Ooh, here's one. Full-text searches. The MyISAM and InnoDB engines both support it but they use different code and implement it differently, so search results may not be compatible.

https://board.phpbuilder.com/d/10402133-free-form-text-search-of-multiple-tables/23

Is that a leftover from your own full-text enhancement efforts?

dalecosp

Weedpacket

Thanks.

We use Sphinx as noted here, so I'm thinking that it's handling most of our worries in that area.