This project is archived and is in readonly mode.
The original TIME ZONE value on PostgreSQL is not correctly restored after going through options :utc and then going back to :local
#4950
The following test case is failing (this happens on certain time zones and using certain dates) ...
1) Failure:
test_timestamp_with_zone_values_without_rails_time_zone_support(PostgresqlDataTypeTest)
[./test/cases/datatype_test_postgresql.rb:237:in `test_timestamp_with_zone_values_without_rails_time_zone_support'
/home/santiago/Documentos/WyeWorks/Proys/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:67:in `__send__'
/home/santiago/Documentos/WyeWorks/Proys/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:67:in `run'
/home/santiago/Documentos/WyeWorks/Proys/rails/activesupport/lib/active_support/callbacks.rb:413:in `_run_setup_callbacks'
/home/santiago/Documentos/WyeWorks/Proys/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:65:in `run']:
expected but was
.
Fix provided on this patch
-
postgresql-tz.patch
2.73 KB
-
Santiago Pastorino- Assigned user set to José Valim
-
Repository
- State changed from verified to committed
(from [7a7c608a26f03abb1245ff83d4e25040ad09cb44]) Your original TIME ZONE value on PostgreSQL is correctly restored now, after going through options :utc and then going back to :local
[#4950 The original TIME ZONE value on PostgreSQL is not correctly restored after go... state:committed]
Signed-off-by: José Valim jose.valim@gmail.com
http://github.com/rails/rails/commit/7a7c608a26f03abb1245ff83d4e250... -
