Jon Leighton 3b8a7cf2a7 Stop trying to be clever about when to define attribute methods. ... There is no meaningful performance penalty in defining attribute methods, since it only happens once. There is also no reason *not* to define them, since they get thrown in an included module, so they will not 'overwrite' anything. In fact, this is desirable, since it allows us to call super.		2011-09-14 00:00:37 +01:00
..
active_record/connection_adapters	introduce a fake AR adapter for mocking database return values	2011-02-04 13:34:57 -08:00
assets	move assets and models	2008-01-18 07:27:03 +00:00
cases	Stop trying to be clever about when to define attribute methods.	2011-09-14 00:00:37 +01:00
fixtures	restores the API docs of AR::Fixtures, made a quick pass over them, revises link in fixture template [closes #2840]	2011-09-03 15:20:30 -07:00
migrations	in the middle of refactoring	2010-12-03 12:00:09 -08:00
models	Raise error when using write_attribute with a non-existent attribute.	2011-09-13 00:01:58 +01:00
schema	Raise error when using write_attribute with a non-existent attribute.	2011-09-13 00:01:58 +01:00
support	Add require 'pathname' as it has not already been required in some circumstances	2011-06-17 14:55:34 +01:00
.gitignore	Refactor Active Record test connection setup. Please see the RUNNING_UNIT_TESTS file for details, but essentially you can now configure things in test/config.yml. You can also run tests directly via the command line, e.g. ruby path/to/test.rb (no rake needed, uses default db connection from test/config.yml). This will help us fix the CI by enabling us to isolate the different Rails versions to different databases.	2011-06-04 23:47:03 +01:00
config.example.yml	more oracle fixes	2011-06-06 15:47:29 -07:00
config.rb	Merge branch 'ar-test-cleanup' of git://git.geeksomnia.com/rails	2008-01-21 17:20:51 +00:00