# Acts\_as\_nested\_set having a different query in production and in developoment

**URL:** <https://www.ruby-forum.com/t/acts-as-nested-set-having-a-different-query-in-production-and-in-developoment/119549>\
**Category:** Rails\
**Created:** [November 7, 2007, 9:51pm UTC](https://www.ruby-forum.com/t/acts-as-nested-set-having-a-different-query-in-production-and-in-developoment/119549 "2007-11-07T21:51:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![whitewolfaustria](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/bbce88/32.png) [@whitewolfaustria](https://www.ruby-forum.com/u/whitewolfaustria)\
**Post date:** [November 7, 2007, 9:51pm UTC](https://www.ruby-forum.com/t/acts-as-nested-set-having-a-different-query-in-production-and-in-developoment/119549/1 "2007-11-07T21:51:49Z")

</div>

Hi all

I have a set up that works in development but not in production and it  
all comes down to a query that is generated by rails.

[4;36;1mGreenRoom Load Including Associations (0.000000) [0m  
[0;1mSELECT green\_rooms.`id` AS t0\_r0, green\_rooms.`green_room` AS  
t0\_r1, green\_rooms.`team_level_id` AS t0\_r2,  
green\_rooms.`organizational_area_id` AS t0\_r3, green\_rooms.`meeting`  
AS t0\_r4, green\_rooms.`parent_id` AS t0\_r5, green\_rooms.`created_by`  
AS t0\_r6, green\_rooms.`created_at` AS t0\_r7, green\_rooms.`updated_by`  
AS t0\_r8, green\_rooms.`updated_at` AS t0\_r9, green\_rooms.`comment` AS  
t0\_r10, green\_rooms.`lock_version` AS t0\_r11,  
organizational\_areas.`id` AS t1\_r0,  
organizational\_areas.`org_area_name` AS t1\_r1, team\_levels.`id` AS  
t2\_r0, team\_levels.`level` AS t2\_r1, parents\_green\_rooms.`id` AS  
t3\_r0, parents\_green\_rooms.`green_room` AS t3\_r1,  
parents\_green\_rooms.`team_level_id` AS t3\_r2,  
parents\_green\_rooms.`organizational_area_id` AS t3\_r3,  
parents\_green\_rooms.`meeting` AS t3\_r4,  
parents\_green\_rooms.`parent_id` AS t3\_r5,  
parents\_green\_rooms.`created_by` AS t3\_r6,  
parents\_green\_rooms.`created_at` AS t3\_r7,  
parents\_green\_rooms.`updated_by` AS t3\_r8,  
parents\_green\_rooms.`updated_at` AS t3\_r9,  
parents\_green\_rooms.`comment` AS t3\_r10,  
parents\_green\_rooms.`lock_version` AS t3\_r11 FROM green\_rooms LEFT  
OUTER JOIN organizational\_areas ON organizational\_areas.id =  
green\_rooms.organizational\_area\_id LEFT OUTER JOIN team\_levels ON  
team\_levels.id = green\_rooms.team\_level\_id LEFT OUTER JOIN green\_rooms  
parents\_green\_rooms ON parents\_green\_rooms.id = green\_rooms.parent\_id  
WHERE (green\_rooms.parent\_id = ‘4’) LIMIT 0, 15 [0m

^[[4;36;1mGreenRoom Load Including Associations (0.000872)^[[0m  
^[[0;1mSELECT green\_rooms.`id` AS t0\_r0, green\_rooms.`green_room` AS  
t0\_r1, green\_rooms.`team_level_id` AS t0\_r2,  
green\_rooms.`organizational_area_id` AS t0\_r3, green\_rooms.`meeting`  
AS t0\_r4, green\_rooms.`parent_id` AS t0\_r5, green\_rooms.`created_by`  
AS t0\_r6, green\_rooms.`created_at` AS t0\_r7, green\_rooms.`updated_by`  
AS t0\_r8, green\_rooms.`updated_at` AS t0\_r9, green\_rooms.`comment` AS  
t0\_r10, green\_rooms.`lock_version` AS t0\_r11,  
organizational\_areas.`id` AS t1\_r0,  
organizational\_areas.`org_area_name` AS t1\_r1, team\_levels.`id` AS  
t2\_r0, team\_levels.`level` AS t2\_r1, childrens\_green\_rooms.`id` AS  
t3\_r0, childrens\_green\_rooms.`green_room` AS t3\_r1,  
childrens\_green\_rooms.`team_level_id` AS t3\_r2,  
childrens\_green\_rooms.`organizational_area_id` AS t3\_r3,  
childrens\_green\_rooms.`meeting` AS t3\_r4,  
childrens\_green\_rooms.`parent_id` AS t3\_r5,  
childrens\_green\_rooms.`created_by` AS t3\_r6,  
childrens\_green\_rooms.`created_at` AS t3\_r7,  
childrens\_green\_rooms.`updated_by` AS t3\_r8,  
childrens\_green\_rooms.`updated_at` AS t3\_r9,  
childrens\_green\_rooms.`comment` AS t3\_r10,  
childrens\_green\_rooms.`lock_version` AS t3\_r11 FROM green\_rooms LEFT  
OUTER JOIN organizational\_areas ON organizational\_areas.id =  
green\_rooms.organizational\_area\_id LEFT OUTER JOIN team\_levels ON  
team\_levels.id = green\_rooms.team\_level\_id LEFT OUTER JOIN green\_rooms  
childrens\_green\_rooms ON childrens\_green\_rooms.parent\_id =  
green\_rooms.id WHERE (green\_rooms.id = ‘3’) AND green\_rooms.id IN  
(‘3’) ^[[0m

the first query is in development and the second is in production.  
The major difference is parent being replace with children and it  
looks at green\_rooms from an eager loading query .

Any reason why this is happening or how to fix it will be  
apprieciated.

White W.

---

<div class="post-metadata">

**Author:** ![whitewolfaustria](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/bbce88/32.png) [@whitewolfaustria](https://www.ruby-forum.com/u/whitewolfaustria)\
**Post date:** [November 8, 2007, 2:27pm UTC](https://www.ruby-forum.com/t/acts-as-nested-set-having-a-different-query-in-production-and-in-developoment/119549/2 "2007-11-08T14:27:45Z")

</div>

This was an active scaffold issue where it was generating the correct  
reverse association , when I added the reverse association in the  
active scaffold config, it works.

White W.