Cache clear new doc ID on rename

[abnegate]

Summary by CodeRabbit

• Bug Fixes
  • Improved cache handling to ensure updated documents with changed identifiers are properly refreshed.

[coderabbitai]

📝 Walkthrough

Walkthrough

The update enhances cache management in the Database class by adding logic to purge the cache for a new document ID when the document's ID changes during an update operation, ensuring both old and new IDs are properly invalidated.

Changes

Cohort / File(s)	Summary
Cache Purge Enhancement src/Database/Database.php	Added conditional cache purge for the new document ID when it differs from the original ID during document updates, preventing stale cache entries for the renamed document.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 When documents dance and change their names,
The cache must follow, no more games!
A purge, a sweep, both old and new,
Our database stays forever true. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Cache clear new doc ID on rename' accurately describes the main change: adding cache purging for the new document ID when a document is renamed (ID changes during update).
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-rename-purge

---

No actionable comments were generated in the recent review. 🎉

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}