fix(db): use self.storage() in storage_by_account_id to avoid cache bypass #3385
+1
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When storage_by_account_id misses the BAL layer, it previously called
self.database.storage()directly, bypassing the Cache and Bundle layers. This could return stale data when storage values have been modified in Cache or Bundle but not yet synced to BAL.The fix changes this to call self.storage(), which correctly traverses the full lookup chain: Cache → Bundle → Database. This is consistent with the storage() method implementation and matches the expected behavior documented in the Database trait's default implementation (lines 67-80).