Stack level too deep error in Ruby on Rails

后端 未结 8 2055
再見小時候
再見小時候 2020-12-16 11:00

I\'m having a stack level too deep error using Ruby 1.8.7 with Rails 3.0.4 and with the rails console I performed the following commands.



        
相关标签:
8条回答
  • 2020-12-16 11:56

    I've found the solution to this issue...

    I'm using Rails 3 and my class looks like this (and the problematic methods was this too)

    class Organization < ActiveRecord::Base
      def self.parents
        @organizations = self.find :all, :conditions => ['is_company = ? ',true]
        select_choice = I18n.t("select") + " "+ I18n.t("segments.description")
        @organization_parents = [select_choice]
        for organization in @organizations
          @organization_parents << [organization.name, organization.id]
        end
        return @organization_parents
      end 
      #...
    end
    

    I did have to hack a lot in the code to find out something was wrong with the named_scope on the line

    @organizations = self.find :all, :conditions => ['is_company = ? ',true]
    

    So I had to change it to something like this

    @organizations = Organization.where("is_company = ?",true)
    

    But it was wrong too.. So I decided to add an scope for this below the class name so the final code looks like this:

    class Organization < ActiveRecord::Base
      scope :company, where("is_company = ?",true)
    
      def self.parents
        @organizations = self.company
        select_choice = I18n.t("select") + " "+ I18n.t("segments.description")
        @organization_parents = [select_choice]
        for organization in @organizations
          @organization_parents << [organization.name, organization.id]
        end
        return @organization_parents
      end 
      #...
    end
    

    So using this line with the scope

    @organizations = self.company
    

    it worked flawlessly in every part of the code.

    I was wondering if the named_scope is deprecated when using class methods or they are not supported from now and throws an error and not a warning before

    Thanks for your help Leo

    0 讨论(0)
  • 2020-12-16 11:59

    I got this error when incorrectly creating a has_many relationship like this:

    has_many :foos, through: foo
    

    So don't put the same model as 'through' or it will loop endlessly.

    0 讨论(0)
提交回复
热议问题