count should not be persisted to query

$models = Data::on($conn);

$good = $models->filter(Filter::equal('processed', 'y'))->count();

$bad = $models->filter(Filter::equal('processed', 'n'))->count();

this example gives $bad the same value as $good since it will not be evaluated after query adaption

https://github.com/Icinga/ipl-orm/blob/832d9ff5346ddce2f2ef19919815067a40bc1ec2/src/Query.php#L723

of course this would work:

$models = Data::on($conn);
$good = $models->filter(Filter::equal('processed', 'y'))->count();

$models = Data::on($conn);
$bad = $models->filter(Filter::equal('processed', 'n'))->count();

Best Regards
Nicolas

Start in src/Query.php around line 723 and reproduce the example with two filtered count calls on the same Data query. Trace how count and query adaption affect persisted state; done means the second count reflects its own filter without requiring a new Data::on($conn) instance.