aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/test/cases
diff options
context:
space:
mode:
authorXavier Noria <fxn@hashref.com>2013-04-20 08:52:55 +0200
committerXavier Noria <fxn@hashref.com>2013-04-20 09:08:52 +0200
commitd32ef7c7a5a1e29f64eb3c2240c642c7b0c73f25 (patch)
tree6696eb97a231de85ac7985a051d4c08abe512ff7 /activerecord/test/cases
parent7004f100a1fe5de46217e8293d139235229fdc56 (diff)
downloadrails-d32ef7c7a5a1e29f64eb3c2240c642c7b0c73f25.tar.gz
rails-d32ef7c7a5a1e29f64eb3c2240c642c7b0c73f25.tar.bz2
rails-d32ef7c7a5a1e29f64eb3c2240c642c7b0c73f25.zip
Rewrites a CHANGELOG entry.
The entry is basically copy & paste of the commit message, but the CHANGELOG has a different purpose than Git history, it just communicates what is new: * No need to explain why did the bug happen (unless it is truly relevant). * No need to explain how was the bug fixed. * Whether the user gives new names to columns does not really matter, use of select to cherry-pick a column for example also presented that behaviour. Non-selected attributes are the key, either because they were not included in the selected list, or because they were but with a different alias. * In the case of an attribute alias, what you really want to depict is that respond_to? returns false for the original attribute name.
Diffstat (limited to 'activerecord/test/cases')
0 files changed, 0 insertions, 0 deletions