aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/CHANGELOG.md
Commit message (Collapse)AuthorAgeFilesLines
...
* Merge pull request #3636 from joshsusser/masterJon Leighton2011-11-291-0/+6
|\ | | | | association methods are now generated in modules
| * changelog & docs for GeneratedFeatureMethodsJosh Susser2011-11-271-0/+6
| |
* | Perf fixJon Leighton2011-11-191-0/+5
| | | | | | | | | | | | | | If we're deleting all records in an association, don't add a IN(..) clause to the query. Fixes #3672.
* | Add missing CHANGELOG entry for #3678. Closes #3678.Jon Leighton2011-11-191-0/+4
| |
* | Verify that #3690 has been closed by previous changes to the mysqlJon Leighton2011-11-191-0/+4
|/ | | | | | | | adapters. These tests fail on the v3.1.2 tag. Closes #3690.
* Sync CHANGELOGs from 3-1-stableJon Leighton2011-11-141-0/+21
|
* implements AR::Relation#explainXavier Noria2011-11-051-0/+2
| | | | | | | | | | | | | | | | | | | 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.
* Merge pull request #3525 from kennyj/fix_3440-1Jon Leighton2011-11-051-0/+4
|\ | | | | Fixed an issue id false option is ignored on mysql/mysql2 (fix #3440)
| * Fixed an issue id false option is ignored on mysql/mysql2 (fix #3440)kennyj2011-11-061-0/+4
| |
* | Add ActiveRecord::Relation#uniq for toggling DISTINCT in the SQL queryJon Leighton2011-11-051-0/+16
| |
* | AR changes to support creating ordered (asc, desc) indexesVlad Jebelev2011-11-041-0/+2
|/
* Convert CHANGELOGs to Markdown format.Jon Leighton2011-11-041-0/+6564
Reasons: * Markdown reads well as plain text, but can also be formatted. * It will make it easier for people to read on the web as Github formats the Markdown nicely. * It will encourage a level of consistency when people are writing CHANGELOG entries. The script used to perform the conversion is at https://gist.github.com/1339263