Multiple in_region calls should not collide

[bdunne]

If you do SomeModel.in_my_region.in_region(x)... you won't see any records.

Found this by setting default_scope { in_my_region } on a model. The workaround was to call .unscoped.in_region(x)...

[carbonin]

SomeModel.in_my_region.in_region(x)

In this case are you in region "x" or not? And does that change whether you get records?

I would expect this behavior as long as it returns the correct rows when you're in region 1 and do SomeModel.in_my_region.in_region(1)

Otherwise I would say this is working as expected.

[bdunne]

In this case are you in region "x" or not?

No, my_region and x are different numbers for this issue

[carbonin]

I think this is not a bug then. That would be like saying:

Model.where(:thing => 1).where(:thing => 2) it doesn't really make sense.

[kbrock]

So the issue is that there is a default_scope?

[bdunne]

The issue is that I was using this in a model with a default scope of in_my_region, but on my call I was expecting Model.in_region(another_region_id) to override the default scope. Instead I had to call Model.unscoped.in_region(another_region_id).

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

[kbrock]

@bdunne wonder if we could put unscoped(:region_id) into in_region or something

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation.