| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | Revert "Added ActiveRecord::Base#last_modified to work with the new ↵ | David Heinemeier Hansson | 2011-12-01 | 1 | -1/+0 | |
| | | | | | | | | | fresh_when/stale? conditional get methods from Action Pack" Needless indirection with no added value. This reverts commit 535853e83b9092078035a5abb2aa242fba815c05. | |||||
| * | Added ActiveRecord::Base#last_modified to work with the new ↵ | David Heinemeier Hansson | 2011-12-01 | 1 | -0/+1 | |
| | | | | | fresh_when/stale? conditional get methods from Action Pack | |||||
| * | ActiveRecord::Relation#pluck method | Bogdan Gusiev | 2011-11-30 | 1 | -0/+9 | |
| | | ||||||
| * | Automatic closure of connections in threads is deprecated. For example | Aaron Patterson | 2011-11-29 | 1 | -0/+16 | |
| | | | | | | | | | | | | | | | | | | the following code is deprecated: Thread.new { Post.find(1) }.join It should be changed to close the database connection at the end of the thread: Thread.new { Post.find(1) Post.connection.close }.join Only people who spawn threads in their application code need to worry about this change. | |||||
| * | Deprecate set_locking_column in favour of self.locking_column= | Jon Leighton | 2011-11-29 | 1 | -0/+1 | |
| | | ||||||
| * | Deprecate set_primary_key in favour of self.primary_key= | Jon Leighton | 2011-11-29 | 1 | -0/+1 | |
| | | ||||||
| * | Deprecate set_sequence_name in favour of self.sequence_name= | Jon Leighton | 2011-11-29 | 1 | -0/+1 | |
| | | ||||||
| * | Deprecate set_inheritance_column in favour of self.inheritance_column= | Jon Leighton | 2011-11-29 | 1 | -2/+8 | |
| | | ||||||
| * | Deprecate set_table_name in favour of self.table_name= or defining your own ↵ | Jon Leighton | 2011-11-29 | 1 | -0/+16 | |
| | | | | | method. | |||||
| * | Merge pull request #3636 from joshsusser/master | Jon Leighton | 2011-11-29 | 1 | -0/+6 | |
| |\ | | | | | association methods are now generated in modules | |||||
| | * | changelog & docs for GeneratedFeatureMethods | Josh Susser | 2011-11-27 | 1 | -0/+6 | |
| | | | ||||||
| * | | Perf fix | Jon Leighton | 2011-11-19 | 1 | -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 Leighton | 2011-11-19 | 1 | -0/+4 | |
| | | | ||||||
| * | | Verify that #3690 has been closed by previous changes to the mysql | Jon Leighton | 2011-11-19 | 1 | -0/+4 | |
| |/ | | | | | | | | adapters. These tests fail on the v3.1.2 tag. Closes #3690. | |||||
| * | Sync CHANGELOGs from 3-1-stable | Jon Leighton | 2011-11-14 | 1 | -0/+21 | |
| | | ||||||
| * | implements AR::Relation#explain | Xavier Noria | 2011-11-05 | 1 | -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-1 | Jon Leighton | 2011-11-05 | 1 | -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) | kennyj | 2011-11-06 | 1 | -0/+4 | |
| | | | ||||||
| * | | Add ActiveRecord::Relation#uniq for toggling DISTINCT in the SQL query | Jon Leighton | 2011-11-05 | 1 | -0/+16 | |
| | | | ||||||
| * | | AR changes to support creating ordered (asc, desc) indexes | Vlad Jebelev | 2011-11-04 | 1 | -0/+2 | |
| |/ | ||||||
| * | Convert CHANGELOGs to Markdown format. | Jon Leighton | 2011-11-04 | 1 | -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 | ||||||
 |
index : rails.git | |
| Mirror of official rails repo with custom fixes. | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |