This project is archived and is in readonly mode.

#2337 ✓stale
Elia Schito

ActiveRecord::instance_method_already_implemented? doesn't catch ActiveRecord::Dirty attributes

Reported by Elia Schito | March 25th, 2009 @ 10:19 AM | in 3.x

I've noticed that when a table column overrides the ActiveRecord::Dirty methods ActiveRecord::DangerousAttributeError is not raised (this in my case happens in a legacy schema that has a column named "changed" instead of "updated_at").

I'll prepare a patch as soon as I figure out the right place to hack...

A solution can also be to include the patch in Ticket #1740

Comments and changes to this ticket

  • Jeremy Kemper

    Jeremy Kemper May 4th, 2010 @ 06:48 PM

    • Milestone changed from 2.x to 3.x
  • Santiago Pastorino

    Santiago Pastorino February 2nd, 2011 @ 04:40 PM

    • State changed from “new” to “open”
    • Importance changed from “” to “”

    This issue has been automatically marked as stale because it has not been commented on for at least three months.

    The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

    Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

  • Santiago Pastorino

    Santiago Pastorino February 2nd, 2011 @ 04:40 PM

    • State changed from “open” to “stale”

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