Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

There was a problem

You must be a member of this account.

Logan Bowers's latest activity

Thursday, December 02 2010
4498 Rails loses precision when deserializing timestamps from Postgresql was updated in Ruby on Rails
  • Logan Bowers
    Logan Bowers commented at 9:57 PM

    The loop is just because it will happen eventually. I could have run this code to find an exact fail case and substituted the NOW() call with the exact timestam...

  • Logan Bowers
    Logan Bowers commented at 9:55 PM

    Each time through the loop a single row is updated to an arbitrary time. Then that row is retrieved and the time is converted to a Ruby object. The Ruby object ...

Wednesday, November 03 2010
5915 New "scoped" implementation since v2.3.9 breaks chained scopes with custom me... was updated in Ruby on Rails
  • Logan Bowers
    • Tag set to bug, regression
    by Logan Bowers at 11:43 PM
  • Logan Bowers
    • Assigned user set to José Valim
    by Logan Bowers at 11:35 PM
  • Logan Bowers
    Logan Bowers created the ticket at 11:34 PM

    Using git-bisect, I tracked down an issued to commit bfbdeea, "Use bind instead of instance_exec cause it may be causing memory leaks. Also, provide a simpler a...

5044 Recent named_scope STI fix causes a massive slow down and memory leak was updated in Ruby on Rails
  • Logan Bowers
    Logan Bowers commented at 11:35 PM

    This commit regressed scoped() functionality, please see bug #5915

Thursday, May 06 2010
4498 Rails loses precision when deserializing timestamps from Postgresql was updated in Ruby on Rails
  • Logan Bowers
    Logan Bowers commented at 10:56 PM
    diff --git a/activerecord/lib/active_record/connection_adapters/abstract/schema_definitions.rb b/activerecord/lib/active_record/connection_adapters/abstract/sc...
Thursday, April 29 2010
4498 Rails loses precision when deserializing timestamps from Postgresql was updated in Ruby on Rails
  • Logan Bowers
    • Tag changed from 2.3.5, activerecord, postgresql, timestamp to 2.3.5, activerecord, patch, postgresql, timestamp
    by Logan Bowers at 7:35 PM
  • Logan Bowers
    Logan Bowers commented at 7:35 PM

    The problem does exist in master (as of f4d174b211effd4cd510c1578bdc391852f4d375), this patch should also apply with minimal fuzzing.

  • Logan Bowers
    Logan Bowers commented at 7:32 PM

    Adding a patch that fixes the issue in 2-3-stable. ActiveRecord::ConnectionAdapters::Column#microseconds did an unnecessary conversion to from Rational to float...