Using AR::Base.none in subquery results with no condition unexpectedly

[PikachuEXE]

Listing.none.count => 0

Expected:
Parent.listings.where(id: Listing.none).count => 0

Actual:
Parent.listings.where(id: Listing.none).count => all_record_count

[senny]

@PikachuEXE can you please attach an executable test-case to reproduce? You can use this script as a starting point.

[PikachuEXE]

OK here it is:
http://pastebin.com/VGRrQYHq
All 3 are failing

[senny]

thank you 💛 l

[rails-bot]

This issue has been automatically marked as stale because it has not been commented on for at least
three months.

The resources of the Rails team are limited, and so we are asking for your help.

If you can still reproduce this error on the 4-1-stable, 4-0-stable branches 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.

[PikachuEXE]

@senny Do you have all the information you need?
@rails-bot pings me :P

[guigs]

I'm experiencing this issue too! I'm using where('1 = 0') as a workaround.

[jrproctor]

I am also using the same where('1 = 0') workaround in my project to avoid this bug