Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | all tests passing on mysql2 | Aaron Patterson | 2014-04-09 | 1 | -3/+3 |
| | |||||
* | Fix warnings on mysql2 explain test | Carlos Antonio da Silva | 2013-12-10 | 1 | -3/+3 |
| | |||||
* | Support MySQL 5.7 explain | Yasuo Honda | 2013-12-10 | 1 | -3/+3 |
| | |||||
* | add the query to AR::Relation#explain output | Xavier Noria | 2011-11-25 | 1 | -0/+3 |
| | | | | | | | Rationale: this is more readable if serveral queries are involved in one call. Also, it will be possible to let AR log EXPLAINs automatically in production mode, where queries are not even around. | ||||
* | implements AR::Relation#explain | Xavier Noria | 2011-11-05 | 1 | -0/+23 |
This is a first implementation, EXPLAIN is highly dependent on the database and I have made some compromises. On one hand, the method allows you to run the most common EXPLAIN and that's it. If you want EXPLAIN ANALYZE in PostgreSQL you need to do it by hand. On the other hand, I've tried to construct a string as close as possible to the ones built by the respective shells. The rationale is that IMO the user should feel at home with the output and recognize it at first sight. Per database. I don't know whether this implementation is going to work well. Let's see whether people like it. |