1. 13 Mar, 2014 1 commit
  2. 11 Mar, 2014 1 commit
  3. 30 Jan, 2014 1 commit
  4. 16 Jan, 2014 1 commit
  5. 09 Jan, 2014 1 commit
  6. 06 Jan, 2014 1 commit
    • destroy! now once again calls destroy · 37b941fb
      This is because destroy! is called by :dependent => :destroy association definitions (yes, destroy! and not destroy), which means that associated records of a paranoid object would suddenly go missing... making it very hard to restore them!
      
      So instead, it's now called really_destroy! and destroy! is just an alias for destroy once again
      Ryan Bigg committed
  7. 03 Jan, 2014 2 commits
  8. 17 Dec, 2013 2 commits
  9. 10 Dec, 2013 1 commit
  10. 12 Nov, 2013 1 commit
  11. 24 Oct, 2013 5 commits
  12. 23 Oct, 2013 1 commit
  13. 20 Oct, 2013 1 commit
  14. 11 Oct, 2013 1 commit
  15. 10 Oct, 2013 2 commits
  16. 09 Sep, 2013 1 commit
  17. 08 Jul, 2013 1 commit
  18. 06 Jun, 2013 3 commits
  19. 18 May, 2013 1 commit
  20. 17 May, 2013 1 commit
  21. 22 Apr, 2013 1 commit
  22. 07 Apr, 2013 1 commit
  23. 16 Mar, 2013 1 commit
  24. 25 Feb, 2013 1 commit
  25. 15 Nov, 2012 2 commits
  26. 26 Jun, 2012 1 commit
  27. 26 Jan, 2012 1 commit
  28. 13 Jun, 2011 3 commits