Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community!
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.Start your free trial
Sahil Ambardekar10,306 Points
Is there any advantage to using different engines on a per-table basis?
Would using different engines on tables be practical? What are some different engines and their uses? Can you give me a link to some further reading? Thanks in advance.
Nathan Tallack22,159 Points
With the exception of using Memory for temporary tables (tables that disappear when you log out and are only visible to you during that session) it is pretty much 99.9% sure that you will only ever use the InnoDb engine.
An exception will be if you are running your database on some sort of embedded device (like a rasberry pi or some such thing) and you care about CPU power consumption.
But on a regular dekstop/server system you can be sure you'll never have to worry about power. ;)