[Dbix-class] resultset_attributes, where, undef - wotz up?

[Peter Rabbitson]

On Fri, Jul 16, 2010 at 01:15:34PM +0100, Benjamin Martin wrote:
> Hi mo,
>
> Thanks for the advice.. but sadly it did not work :(
>
> I will put a test case together to see if I can prove what is  
> happening... I guess is should work as it is in the docs.

The whole point of resultset chaining is that it is additive-only, so
when some function passes you a restricted resultset you can *not*
break these restrictions, but are only able to lock them down further.
This is why using {where} resultset attributes is generally discouraged
because there is no way to satisfy "but I want to take it off now"
without breaking the entire paradigm of chaining.

Either register a new source, OR add a resultset *method* which gives
you a restricted subset, and which you use throughout your application.

Cheers