Rails - May 2006 - "Stack Level Too Deep" issue in HABTM Unit / Functional Test

Hello guys. I was able to figure out that my "stack level too deep" 
error I was getting with my HABTM destroy method was the result of a bug 
in rails 1.0. I upgraded to 1.1.2 and now the views and any console-run 
commands for destroying AR objects linked together via HABTM work just 
fine.

I have HABTM setup between stories and submissions.

The issue is that the destroy methods in my unit tests and my functional 
tests are now giving me the "stack level too deep" issue. The unit
test
only does it on the submissions side of the HABTM relationship, but the 
functional test fails on the stories side.

-- 
Posted via http://www.ruby-forum.com/.

Bryan Corey wrote:
> Hello guys. I was able to figure out that my "stack level too
deep"
> error I was getting with my HABTM destroy method was the result of a bug 
> in rails 1.0. I upgraded to 1.1.2 and now the views and any console-run 
> commands for destroying AR objects linked together via HABTM work just 
> fine.
> 
> I have HABTM setup between stories and submissions.
> 
> The issue is that the destroy methods in my unit tests and my functional 
> tests are now giving me the "stack level too deep" issue. The
unit test
> only does it on the submissions side of the HABTM relationship, but the 
> functional test fails on the stories side.
No one? I can''t believe I am the only one that has run into this issue.


-- 
Posted via http://www.ruby-forum.com/.

Bryan,

Plenty of us use HABTM relationships every day and don''t have this  
problem, so it must be something you''re doing in your code. Given you  
haven''t posted any details of what you''re actually doing (code
and
stack trace), we can''t really help!

On 25/05/2006, at 5:09 AM, Bryan Corey wrote:
> Bryan Corey wrote:
>> Hello guys. I was able to figure out that my "stack level too
deep"
>> error I was getting with my HABTM destroy method was the result of  
>> a bug
>> in rails 1.0. I upgraded to 1.1.2 and now the views and any  
>> console-run
>> commands for destroying AR objects linked together via HABTM work  
>> just
>> fine.
>>
>> I have HABTM setup between stories and submissions.
>>
>> The issue is that the destroy methods in my unit tests and my  
>> functional
>> tests are now giving me the "stack level too deep" issue. The
unit
>> test
>> only does it on the submissions side of the HABTM relationship,  
>> but the
>> functional test fails on the stories side.
>
> No one? I can''t believe I am the only one that has run into this  
> issue.
>
>
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails