Model.destroy_all might not destroy all

[trym]

After doing Update.destroy_all I had one update left, which went away when I did Update.destroy_all again.

[thhermansen]

Don't think this is related to the ORM, as the implementation of destroy_all is really easy (https://github.com/CompanyBook/massive_record/blob/develop/lib/massive_record/orm/persistence.rb)

I think this actually is a wrapper (adapter) problem, as the Scanner applies a default limit of 10: https://github.com/CompanyBook/massive_record/blob/develop/lib/massive_record/wrapper/scanner.rb. Now that's a problem meaning that all will just return 10 and not all .. which should really be corrected.

[thhermansen]

Kinda fixed in 4d23ad8

Maybe we should look at it a bit more later...