Charles G.

Results 3 comments of Charles G.

Looks like you either: a) have a fix for it already (in this pull request: https://github.com/goncalossilva/rails3_acts_as_paranoid/pull/106/files) or b) created the bug on your local dev (in the very same pull...

Be really hard to tell if the bug is in your iterator, or in BoltDB. I have this exact use case implemented, but I use `Bucket.Delete()` while the iterator walks....

From the README, the only mention of deletes is `Use the Bucket.Delete() function to delete a key from the bucket.` I suspect that calling Bucket.Delete() spins up a new Cursor...