This project is archived and is in readonly mode.

#4950 ✓committed
Santiago Pastorino

The original TIME ZONE value on PostgreSQL is not correctly restored after going through options :utc and then going back to :local

Reported by Santiago Pastorino | June 24th, 2010 @ 01:51 AM | in 3.0.2

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

Comments and changes to this ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>

Attachments