- 02 1月, 2014 1 次提交
-
-
由 Jon Leighton 提交于
* Move check from generated helper to test_help.rb, so that all applications can benefit * Rather than just raising when the test schema has pending migrations, try to load in the schema and only raise if there are pending migrations afterwards * Opt out of the check by setting config.active_record.maintain_test_schema = false * Deprecate db:test:* tasks. The test helper is now fully responsible for maintaining the test schema, so we don't need rake tasks for this. This is also a speed improvement since we're no longer reloading the test database on every call to "rake test".
-
- 26 12月, 2013 1 次提交
-
-
由 Łukasz Strzałkowski 提交于
Warning: ~/projects/rails/activerecord/lib/active_record/railtie.rb:140: warning: method redefined; discarding old extend_message ~/projects/rails/activerecord/lib/active_record/errors.rb:104: warning: previous definition of extend_message was here
-
- 24 12月, 2013 3 次提交
-
-
由 José Valim 提交于
-
由 José Valim 提交于
-
由 José Valim 提交于
This commit also cleans up the rake tasks that were checking for DATABASE_URL in different places. In fact, it would be nice to deprecate DATABASE_URL usage in the long term, considering the direction we are moving of allowing those in .yml files.
-
- 23 12月, 2013 1 次提交
-
-
由 schneems 提交于
Currently if you attempt to use a database that does not exist you get an error: ``` PG::ConnectionBad FATAL: database "db_error" does not exist ``` The solution is easy, create and migrate your database however new developers may not know these commands by memory. Instead of requiring the developer to search for a solution, tell them how to fix the problem in the error message: ``` ActiveRecord::NoDatabase: FATAL: database "db_error" does not exist Run `$ bin/rake db:create db:migrate` to create your database ``` Active Record should not know about `rake db:migrate` so this additional information needs to come from the railtie. Potential alternative implementation suggestions are welcome.
-
- 08 8月, 2013 1 次提交
-
-
由 Damien Mathieu 提交于
-
- 02 7月, 2013 2 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
由 Yves Senn 提交于
-
- 23 6月, 2013 2 次提交
-
-
由 Piotr Sarnacki 提交于
Those vars can be used in tasks, which not call load_config.
-
由 Piotr Sarnacki 提交于
In commit d1d7c86d I moved setting migrations paths into activerecord's railtie to remove Rails dependency on databases.rake. However, it introduced a regression, ENGINE_PATH was not available at the moment, so engine's migrations where not added properly to paths. Fix was added at 97a4a771, but it changes a way things work from using ENGINE_PATH to APP_RAKEFILE. Additionally, the config runs when the code loads, while previously it ran in the db:load_config rake task In order to make it more in pair with original version this commit changes the config to run only on load_config task. This code uses the fact that defining a task in rake does not overwrite, but only appends. It also allows to get back to checking for ENGINE_PATH
-
- 16 5月, 2013 2 次提交
-
-
由 Piotr Sarnacki 提交于
-
由 Joel Cogen 提交于
Broken by d1d7c86d
-
- 25 4月, 2013 2 次提交
-
-
由 Piotr Sarnacki 提交于
-
由 Piotr Sarnacki 提交于
This will allow to set fixtures path in global config easier, it should be not needed to use FIXTURES_PATH every time user wants to load fixtures.
-
- 24 4月, 2013 1 次提交
-
-
由 Piotr Sarnacki 提交于
-
- 14 3月, 2013 1 次提交
-
-
由 Vipul A M 提交于
-
- 03 3月, 2013 1 次提交
-
-
由 José Valim 提交于
-
- 25 2月, 2013 1 次提交
-
-
由 Yves Senn 提交于
We discussed that the auto explain feature is rarely used. This PR removes only the automatic explain. You can still display the explain output for any given relation using `ActiveRecord::Relation#explain`. As a side-effect this should also fix the connection problem during asset compilation (#9385). The auto explain initializer in the `ActiveRecord::Railtie` forced a connection.
-
- 20 2月, 2013 1 次提交
-
-
由 Terence Lee 提交于
make connection_url_to_hash a class method This als prevents loading database.yml if it doesn't exist but DATABASE_URL does
-
- 31 12月, 2012 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 29 11月, 2012 3 次提交
-
-
由 Lucas Mazza 提交于
-
由 Rafael Mendonça França 提交于
Rather than just raising a NoMethodError when copying the config, this commit adds a warning message until either the rails-observers gem is installed or the relevant config options are removed.
-
由 Rafael Mendonça França 提交于
They was extracted from a plugin. See https://github.com/rails/rails-observers [Rafael Mendonça França + Steve Klabnik]
-
- 26 11月, 2012 1 次提交
-
-
由 Blake Smith 提交于
-
- 13 11月, 2012 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 09 11月, 2012 1 次提交
-
-
由 Andrew White 提交于
Most apps upgrading from 3.x will have options for mass assigment in their application.rb and environments/*.rb config files. Rather than just raising a NoMethodError when copying the config, this commit adds a warning message until either the protected_attributes gem is installed or the relevant config options are removed.
-
- 26 10月, 2012 1 次提交
-
-
由 Jon Leighton 提交于
In the end I think the pain of implementing this seamlessly was not worth the gain provided. The intention was that it would allow plain ruby objects that might not live in your main application to be subclassed and have persistence mixed in. But I've decided that the benefit of doing that is not worth the amount of complexity that the implementation introduced.
-
- 08 10月, 2012 1 次提交
-
-
由 kennyj 提交于
-
- 24 9月, 2012 1 次提交
-
-
由 Xavier Noria 提交于
-
- 22 9月, 2012 1 次提交
-
-
由 Francesco Rodriguez 提交于
-
- 09 9月, 2012 1 次提交
-
-
由 Arun Agrawal 提交于
-
- 22 8月, 2012 1 次提交
-
-
由 José Valim 提交于
The new option allows any Ruby namespace to be registered and set up for eager load. We are effectively exposing the structure existing in Rails since v3.0 for all developers in order to make their applications thread-safe and CoW friendly.
-
- 01 8月, 2012 1 次提交
-
-
由 kennyj 提交于
-
- 16 6月, 2012 4 次提交
-
-
由 Jon Leighton 提交于
-
由 Jon Leighton 提交于
-
由 Jon Leighton 提交于
Get rid of ActiveModel::Configuration, make better use of ActiveSupport::Concern + class_attribute, etc.
-
由 Jon Leighton 提交于
-
- 10 6月, 2012 1 次提交
-
-
由 schneems 提交于
can be configured by setting config.active_record.migration. Setting to :page_load will raise an error on each page refresh if there are migrations that are pending. Setting to :page_load is defaulted in development for new applications.
-
- 29 5月, 2012 1 次提交
-
-
由 kennyj 提交于
-