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.

This project is archived and is in readonly mode.

Loading fixtures for a module's model

#1628

The load of fixtures doesn't detect models includes in modules so :

module RailsCommerce class Product < ActiveRecord::Base end end

We should to specify :

set_fixture_class :rails_commerce_products => RailsCommerce::Product

This patch detects automatically modules.

Reported by Jonathan Démoutiez · December 24th, 2008 @ 02:49 PM

State: stale
Milestone: 3.x
Assigned to: Michael Koziarski Michael Koziarski
Importance: none

Activity

  1. Pratik
    Pratik
    • Assigned user set to Michael Koziarski
    • Tag changed from activerecord, fixtures, models, modules to activerecord, fixtures, models, modules, patch

    March 7th, 2009 @ 01:58 PM

  2. kmpm
    kmpm

    Bumping this one and sending along a reminder to look at #1976 which deals with namespaces in scaffold generator.

    July 22nd, 2009 @ 04:21 PM

  3. kmpm
    kmpm

    Seems related to #675 "fixtures: consider fixture_class_names to find fixture_class file"

    July 27th, 2009 @ 11:11 AM

  4. José Valim
    José Valim

    As Koz said in #1976, modules should not be prefixed with table_names:

    module RailsCommerce
      class Product < ActiveRecord::Base
      end
    end
    
    RailsCommerce::Product.table_name #=> "products"
    

    So we have two issues:

    1) fixtures cannot be loaded when a set_table_name is used in the model
    2) fixtures cannot be loaded when using modules (see #2965)

    Your ticket solves a special condition when both problems happen: you use modules and set the table name in them.

    August 15th, 2009 @ 08:47 PM

  5. Jeremy Kemper
    Jeremy Kemper
    • Milestone changed from 2.x to 3.x

    May 4th, 2010 @ 06:48 PM

  6. Santiago Pastorino
    Santiago Pastorino
    • 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.

    February 2nd, 2011 @ 04:42 PM

  7. Santiago Pastorino
    Santiago Pastorino
    • State changed from open to stale

    February 2nd, 2011 @ 04:42 PM