Arrange returning child elements at top level and not nesting within parent about ancestry

[stefankroes]

Your categories have not been nested properly. Check Category.find_by_name("Albacore").parent , it is probably nil.

On 5 jul 2011, at 16:34, jperrine wrote:

I have a rails 3.0.7 app with categories that are being nested within themselves using ancestry.

Steps to reproduce

Given I have the following categories nested within a category named "Health & Beauty"
Category "Albacore"
Category "Cream"

Calling Category.arrange returns the following nested hash

{
#<Category id: 37, name: "Albacore", created_at: "2011-07-05 14:27:30", updated_at: "2011-07-05 14:27:30", ancestry: "25">=>{},
#<Category id: 25, name: "Beauty and Hygiene", created_at: "2011-07-01 14:21:00", updated_at: "2011-07-01 14:21:00", ancestry: nil> =>
{
#<Category id: 38, name: "Cream", created_at: "2011-07-05 14:27:37", updated_at: "2011-07-05 14:27:37", ancestry: "25">=>{}
}
}

When I expect both "Cream" and "Albacore" to be returned within the "Beauty and Hygiene" ordered hash.

Reply to this email directly or view it on GitHub:
#60

[jperrine]

Category.find_by_name("Albacore").parent
 => #<Category id: 25, name: "Beauty and Hygiene", created_at: "2011-07-01 14:21:00", updated_at: "2011-07-01 14:21:00", ancestry: nil> 

It's nested properly, you can see the ancestry column in my original post which correctly has the id for "Beauty and Hygiene"

[stefankroes]

Do you by any chance have a default scope that includes sorting?

If so change (example)

default_scope order(:name)

to (example)

default_scope order_by_ancestry_and(:name)

Alternatively you can use:

Category.with_exclusive_scope.arrange

Stefan

On 6 jul 2011, at 14:03, jperrine wrote:

Category.find_by_name("Albacore").parent
=> #<Category id: 25, name: "Beauty and Hygiene", created_at: "2011-07-01 14:21:00", updated_at: "2011-07-01 14:21:00", ancestry: nil>

It's nested properly, you can see the ancestry column in my original post which correctly has the id for "Beauty and Hygiene"

Reply to this email directly or view it on GitHub:
#60 (comment)

[jperrine]

That was the problem, thanks!