- 02 8月, 2013 8 次提交
-
-
由 Aaron Patterson 提交于
decouple the builder classes from the model. Builder objects should be easier to reuse now.
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 01 8月, 2013 4 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 03 7月, 2013 1 次提交
-
-
由 Neeraj Singh 提交于
-
- 02 7月, 2013 2 次提交
-
-
由 Neeraj Singh 提交于
-
由 Neeraj Singh 提交于
Deprecated options `delete_sql`, `insert_sql`, `finder_sql` and `counter_sql` have been deleted.
-
- 15 5月, 2013 1 次提交
-
-
由 aditya-kapoor 提交于
Added some more documentation for define_readers and define_writer of the Association and its inherited classes
-
- 18 1月, 2013 1 次提交
-
-
由 Jon Leighton 提交于
Suggested by @dhh. It doesn't affect the generated SQL, so seems reasonable to continue to allow it as an association option.
-
- 07 11月, 2012 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 11 8月, 2012 3 次提交
-
-
由 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.
-
由 Jon Leighton 提交于
-
由 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.
-
- 03 8月, 2012 1 次提交
-
-
由 Xavier Noria 提交于
-
- 02 8月, 2012 2 次提交
-
-
由 Jon Leighton 提交于
-
由 Jon Leighton 提交于
This reverts commit 3803fcce. Conflicts: activerecord/CHANGELOG.md It will be deprecated only in 4.0, and removed properly in 4.1.
-
- 21 7月, 2012 1 次提交
-
-
由 Jon Leighton 提交于
-
- 14 7月, 2012 3 次提交
-
-
由 Jon Leighton 提交于
-
由 Jon Leighton 提交于
-
由 Jon Leighton 提交于
-
- 13 7月, 2012 1 次提交
-
-
由 Jon Leighton 提交于
-
- 06 1月, 2012 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 28 11月, 2011 1 次提交
-
-
由 Josh Susser 提交于
This change uses Module.redefine_method as defined in ActiveSupport. Making Module.define_method public would be as clean in the code, and would also emit warnings when redefining an association. That is pretty messy given current tests, so I'm leaving it for someone else to decide what approach is better.
-
- 16 11月, 2011 1 次提交
-
-
由 Josh Susser 提交于
Instead of generating association methods directly in the model class, they are generated in an anonymous module which is then included in the model class. There is one such module for each association. The only subtlety is that the generated_attributes_methods module (from ActiveModel) must be forced to be included before association methods are created so that attribute methods will not shadow association methods.
-
- 22 2月, 2011 1 次提交
-
-
由 Jon Leighton 提交于
Use proper objects to do the work to build the associations (adding methods, callbacks etc) rather than calling a whole bunch of methods with rather long names.
-