1. 03 10月, 2013 4 次提交
  2. 04 9月, 2013 1 次提交
  3. 02 8月, 2013 10 次提交
  4. 01 8月, 2013 3 次提交
  5. 24 7月, 2013 1 次提交
  6. 23 7月, 2013 5 次提交
  7. 03 7月, 2013 1 次提交
  8. 12 6月, 2013 2 次提交
  9. 20 5月, 2013 1 次提交
  10. 15 5月, 2013 3 次提交
  11. 29 11月, 2012 1 次提交
  12. 11 8月, 2012 6 次提交
    • J
      Use method compilation for association methods · 6e57d5c5
      Jon Leighton 提交于
      Method compilation provides better performance and I think the code
      comes out cleaner as well.
      
      A knock on effect is that methods that get redefined produce warnings. I
      think this is a good thing. I had to deal with a bunch of warnings
      coming from our tests, though.
      6e57d5c5
    • J
      DRY up handling of dependent option · 6bb8afb4
      Jon Leighton 提交于
      6bb8afb4
    • J
      Unprivatise all the things · 825c05d4
      Jon Leighton 提交于
      Well, not all of them, but some of them.
      
      I don't think there's much reason for these methods to be private.
      825c05d4
    • J
      move dependency logic out of generated methods · ea8181b6
      Jon Leighton 提交于
      ea8181b6
    • J
      Clean up dependent option validation. · 08fb3c8f
      Jon Leighton 提交于
      We don't need the complexity of to_sentence, and it shouldn't be a bang
      method.
      08fb3c8f
    • J
      Remove the dependent_restrict_raises option. · 5ad79989
      Jon Leighton 提交于
      It's not really a good idea to have this as a global config option. We
      should allow people to specify the behaviour per association.
      
      There will now be two new values:
      
      * :dependent => :restrict_with_exception implements the current
        behaviour of :restrict. :restrict itself is deprecated in favour of
        :restrict_with_exception.
      * :dependent => :restrict_with_error implements the new behaviour - it
        adds an error to the owner if there are dependent records present
      
      See #4727 for the original discussion of this.
      5ad79989
  13. 01 8月, 2012 2 次提交