Added tenant to the result in find so that result contains tenant and we get access to tenant in the document

[ArnabChatterjee20k]

Summary by CodeRabbit

• Bug Fixes
  • Ensured the tenant field is correctly included and reflected in database query results.
• Tests
  • Enhanced test coverage to verify tenant field consistency in shared table scenarios.

[coderabbitai]

Warning

Rate limit exceeded

@ArnabChatterjee20k has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 59 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between ac70b5b and 43aa35c.

📒 Files selected for processing (2)

• src/Database/Adapter/MariaDB.php (1 hunks)
• src/Database/Adapter/Postgres.php (1 hunks)

Walkthrough

The changes update the MariaDB and Postgres adapters' find methods to explicitly assign the $tenant field back into each document in the results array. The testEmptyTenant test is enhanced with a conditional block for shared tables to verify tenant consistency between query results and document retrieval.

Changes

File(s)	Change Summary
src/Database/Adapter/MariaDB.php,	Ensures $tenant field is explicitly assigned to each result document in the find method.
src/Database/Adapter/Postgres.php
tests/e2e/Adapter/Scopes/DocumentTests.php	Adds a conditional test block for shared tables in testEmptyTenant to check tenant consistency.

Poem

In the garden of code, a tenant appears,
Now safely returned, allaying old fears.
Tests peek and compare, in tables they roam,
Ensuring each document finds the right home.
With every new check, our confidence grows—
The database rabbit hops where accuracy flows! 🐇✨

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between aa0116b and 7d2b9f3.

📒 Files selected for processing (2)

• src/Database/Adapter/MariaDB.php (1 hunks)
• tests/e2e/Adapter/Scopes/DocumentTests.php (1 hunks)

🔇 Additional comments (2)

src/Database/Adapter/MariaDB.php (1)

1662-1666: LGTM! Critical fix for tenant data accessibility.

This change correctly ensures that the processed $tenant field is assigned back to the results array. Without this line, the tenant information would be processed but lost, which could break tenant isolation in multi-tenant applications using shared tables.

The fix follows the established pattern used for other internal fields ($id, $sequence, etc.) and resolves the issue described in the PR objectives.

tests/e2e/Adapter/Scopes/DocumentTests.php (1)

4248-4251: ```shell
#!/bin/bash

Locate Query::select implementation with accurate line number

echo "🔍 Locating Query::select definition with line number:"
rg -n "public static function select" src/Database/Query.php | head -n1

LINE=$(rg -n "public static function select" src/Database/Query.php | head -n1 | cut -d: -f1)
echo
echo "📄 Showing Query::select implementation (from line $LINE):"
sed -n "${LINE},$((LINE+20))p" src/Database/Query.php

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->