This is a discussion on ANN assert_efficient_sql within the MySQL Database forums, part of the Database Forums category; To ensure your test cases call efficient MySQL... def test_my_case assert_efficient_sql do # just wrap them in this block! end end ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
To ensure your test cases call efficient MySQL...
def test_my_case assert_efficient_sql do # just wrap them in this block! end end The assertion intercepts and copies out your MySQL SELECT statements, then calls EXPLAIN on each one, and inspects the results for common problems. The goal is test cases that resist database pessimization, even as you change your data relations, to add new features. If you run your tests after every few changes, you can easily detect which change broke your database's indices and relations. Blog: http://www.oreillynet.com/ruby/blog/...cient_sql.html RDocs: http://efficient-sql.rubyforge.org/ A critique: http://enfranchisedmind.com/blog/200...efficient_sql/ -- Phlip |
![]() |
| Thread Tools | |
| Display Modes | |
|
|