Deleted models leave behind their Collection keys. about johm HOT 5 CLOSED

Only Arrays where supported while deleting a model and its children. I'm adding support for the other various collections (CollectionList, CollectionSet and so on).

Now @zTristan in your example, you're just checking that the key Test:1:messages has been deleted but not that TestMessage:1 (which was contained in Test:1:messages) has been deleted also, is that the behaviour you were expecting at first sight ?

from johm.

I have done some improvments in my fork, I think I already solved this issue. Give me few days to make a pull request because I have done other changes. Some of them are:

• @SupportAll - id removal from collection when deleting
• Sentinel support - so JOhm can be used with HA Redis/Sentinel

from johm.

Sorry my Github mails were in my spam I did not notice your issue before!
I will look into it.

from johm.

I just released version 0.6.7 including the latest pull requests from @dpoldrugo and the fix for issue #9 and #5.

from johm.

Now @zTristan in your example, you're just checking that the key Test:1:messages has been deleted but not that TestMessage:1 (which was contained in Test:1:messages) has been deleted also, is that the behaviour you were expecting at first sight ?

@agrison yes, it was just the indexes for the collection. They were being left behind with no expire. The TestMessages still needed to be manually deleted.

Thanks for the update! I'll pull down 0.6.7 and verify!

from johm.