3 ms·
Meh, it's not so much MySQL that's lame in this case, it's just the MyISAM engine, which depressingly enough is still common in 2009. MyISAM is based on IBM ma
by spudlyo 17y ago
Meh, it's not so much MySQL that's lame in this case, it's just the MyISAM engine, which depressingly enough is still common in 2009. MyISAM is based on IBM mainframe database technology developed back in the stone age. The InnoDB engine doesn't have these kinds of locking issues.
Getting Drupal to run on a non-MySQL database is non-trivial. Here's an interesting article detailing what folks at Oracle had to do to get it to run on Oracle.
http://www.oracle.com/technology/pub/articles/pedros-drupal.html http://www.oracle.com/technology/pub/articles/pedros-drupal....
- sauce71 17y agoThe article was written about an effort using Drupal 4 ... and it turned out to be suprisingly easy due to the structured nature of the Drupal database api. Did you read the stuff??
- spudlyo 17y agoI stand behind my use of the phrase "non-trivial". The fact that Drupal has a reasonably clean DB communication layer that separates out bind variables to avoid injection attacks was why they didn't give up on the project at the start. I doubt anyone involved in the project would describe the effort as "surprisingly easy".