The Design of Software (CLOSED)

A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.

The "Design of Software" discussion group has been merged with the main Joel on Software discussion group.

The archives will remain online indefinitely.

MySQL:  Compound Key Optimisation

Hey All,

I recall, vaguely, that MySQL was suboptimal at dealing with large tables when using a compound primary key.

Is this at all correct and if so, why?

- James.
James Birchall Send private email
Thursday, September 28, 2006
 
 
I have never used MySQL, but it is my impression that it is still one of the fastest databases to use, though historically it has made many sacrifices for this speed. (Such as sacrificing ACID compliance)

I am also under the impression that you can redefine how it stores and manages the tables on a per-table basis, so you could choose a different mechanism, which has different disadvantages and advantages.
Arafangion Send private email
Thursday, September 28, 2006
 
 
I've never heard that but then I haven't heard every rumour.  It might be true, it might not.  It might have been true 3 years ago and no longer true now. 

Why are you asking the question?
Almost H. Anonymous Send private email
Friday, September 29, 2006
 
 
1) Define "optimal".
2) Provide proof that MySQL is "suboptimal".
Tony Marston Send private email
Friday, September 29, 2006
 
 
Testing these hypotheses is generally trivially easy.
David Aldridge Send private email
Saturday, September 30, 2006
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz