This project is archived and is in readonly mode.

#2867 ✓stale

ActiveRecord fixtures don't respect database connection when quoting

Reported by mck | July 3rd, 2009 @ 02:07 PM | in 3.x

The method Fixtures.create_fixtures(...) takes a connection as a block. But then the class Fixture is not respecting the given connection when quoting, so the generated SQL fails if the adapters differ (Here: PostgreSQL -> MySQL).

Comments and changes to this ticket

  • Jeremy Kemper

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

    • Milestone changed from 2.x to 3.x
  • Dan Pickett

    Dan Pickett May 9th, 2010 @ 07:20 PM

    • Assigned user set to “Ryan Bigg”

    I wasn't able to access this patch. This should be designated as stale or incomplete.

  • Ryan Bigg

    Ryan Bigg May 9th, 2010 @ 10:12 PM

    • State changed from “new” to “incomplete”
    • Assigned user cleared.
  • mck

    mck May 11th, 2010 @ 09:16 AM

    I uploaded the patch again. The issue is fixed in activerecord-2.3.5.

  • Santiago Pastorino

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

    • State changed from “incomplete” 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:39 PM

    • State changed from “open” to “stale”
  • mck

    mck February 9th, 2011 @ 04:23 PM

    I checked it in the 3.0 branch and the issue is fixed. this ticket can be closed.

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