- 27 1月, 2013 3 次提交
-
-
由 Lucas Mazza 提交于
`Kernel.quietly` silences `STDOUT` and `STDERR`, which is useless if the logger is writing to a file, while `AS::Logger#silence` swaps the logger level to `ERROR`. Related to #8820 and #8052.
-
由 Andrew White 提交于
With the addition of String#in_time_zone and Date#in_time_zone we can simplify the type casting code by checking if the value has an `in_time_zone` method.
-
由 Lilibeth De La Cruz 提交于
Previously, when `time_zone_aware_attributes` were enabled, after changing a datetime or timestamp attribute and then changing it back to the original value, `changed_attributes` still tracked the attribute as changed. This caused `[attribute]_changed?` and `changed?` methods to return true incorrectly. Example: in_time_zone 'Paris' do order = Order.new original_time = Time.local(2012, 10, 10) order.shipped_at = original_time order.save order.changed? # => false # changing value order.shipped_at = Time.local(2013, 1, 1) order.changed? # => true # reverting to original value order.shipped_at = original_time order.changed? # => false, used to return true end
-
- 26 1月, 2013 1 次提交
-
-
由 Yves Senn 提交于
closes #6865
-
- 25 1月, 2013 2 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 24 1月, 2013 2 次提交
-
-
由 Akira Matsuda 提交于
or the ConnectionPool silently fails to close connections inside the Thread
-
由 Andrew White 提交于
Travis only has PostgreSQL 9.1.x but 9.2 is required for range datatypes.
-
- 23 1月, 2013 1 次提交
-
-
由 bUg 提交于
-
- 22 1月, 2013 7 次提交
-
-
由 Andrew White 提交于
This reverts commit e9d2ad39. Closes #8460 Conflicts: activerecord/lib/active_record/attribute_methods/time_zone_conversion.rb activerecord/test/cases/dirty_test.rb
-
由 Rafael Mendonça França 提交于
[ci skip]
-
由 Akira Matsuda 提交于
-
由 Tatsuro Baba 提交于
-
由 Akira Matsuda 提交于
-
由 Akira Matsuda 提交于
-
由 wangjohn 提交于
Refactored transaction state into its own object. Each transaction creates a new transaction state object upon initialization.
-
- 21 1月, 2013 2 次提交
- 20 1月, 2013 1 次提交
-
-
由 David 提交于
-
- 19 1月, 2013 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
* User class instead of Users. * #where_values_hash does not change the value to downcase as the example was showing. [ci skip]
-
- 18 1月, 2013 7 次提交
-
-
由 Guillermo Iguaran 提交于
This reverts commit 637a7d9d, reversing changes made to 5937bd02.
-
由 robertomiranda 提交于
-
由 Jon Leighton 提交于
Suggested by @dhh. It doesn't affect the generated SQL, so seems reasonable to continue to allow it as an association option.
-
由 Jon Leighton 提交于
Fixes #8795
-
由 Tatsuro Baba 提交于
I think that these signs are probably mistake.
-
由 Xavier Noria 提交于
This revision makes crystal clear that the methods go straight to the database and update the receiver. It also adds and example, and removes the duplication in the singular and plural forms by referring one to the other.
-
由 Carlos Antonio da Silva 提交于
There's no need to create a new arel table or reflect on the column association if the value is empty, these attributes are not used. Also no need to concat a new array, just append the query value.
-
- 17 1月, 2013 1 次提交
-
-
由 Jonathan Garvin 提交于
-
- 16 1月, 2013 2 次提交
-
-
由 Vitor Baptista 提交于
If we set encoding latin1 for a PostgreSQL database, it calls PostgreSQLAdapter::create_database with options that have, among other things: { 'encoding' => 'latin1' } Then, we use reverse_merge(:encoding => "utf8") to setup the default encoding. In the end, the hash looks like: { :encoding => 'utf8', 'encoding' => 'latin1' } The call to options.symbolize_keys calls to_sym on each_key of this Hash. It usually means that the encoding passed overwrites the default utf8, but it's not guaranteed. So, we shouldn't rely on it. The same was happening in ActiveRecord::ConnectionHandling.
-
由 Carlos Antonio da Silva 提交于
This reverts commit 8348f9ea, reversing changes made to 9dfe2d6f. Reason: this broke railties tests as explained in the issue, and the author is going to review and report back. https://github.com/rails/rails/pull/8930#issuecomment-12272671
-
- 15 1月, 2013 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
We were previously rescuing "nil" when no exception class was found. This does work in 1.9.3, but does not in 2.0, raising an exception asking for a class or module to be given to the rescue clause. Thanks @yahonda for catching this.
-
- 14 1月, 2013 1 次提交
-
-
由 Slava Kravchenko 提交于
-
- 13 1月, 2013 1 次提交
-
-
由 Yves Senn 提交于
-
- 12 1月, 2013 3 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
由 Carlos Antonio da Silva 提交于
When running tasks such "rake db:setup", instead of showing messages like "db_development already exists", it was showing a big stack trace and a message "Couldn't create database for ..." with the configuration options, a very confusing message with a big trace. This brings back the functionality present in 3-2, showing the same message.
-
由 Derek Kraan 提交于
in a default_scope. `Model.joins(...).where(condition_on_joined_table).update_all` / `delete_all` worked, but the same operation implemented with a default_scope generated a SQL error because ActiveRecord ignored the join but implemented the where condition anyways.
-
- 09 1月, 2013 2 次提交
-
-
由 Angelo Capilleri 提交于
-
由 Angelo Capilleri 提交于
-
- 08 1月, 2013 2 次提交
-
-
由 Carlos Antonio da Silva 提交于
Some tests were raising the following error: Could not log "sql.active_record" event. NoMethodError: undefined method `type' for nil:NilClass` Due to the way binds were being logged, the column info was considered always present, but that is not true for some of the tests listed in the issue. Closes #8806.
-
由 Angelo capilleri 提交于
-