This project is archived and is in readonly mode.

#6702 new
James Prior

New STI classes should not be marked as dirty

Reported by James Prior | April 14th, 2011 @ 04:38 AM

By default, a newly created class is not marked dirty => false

But a newly created STI class is

  class LiveParrot < Parrot
  end => true

The included patch for dirty.rb is for the rails 2.3 branch and attempts to follow the pattern established in the dirty module to ignore any changes to the STI column when initializing a new record.

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=""></a>

People watching this ticket