fix(db): add tenant_id to save_public_agent_message function#38
fix(db): add tenant_id to save_public_agent_message function#38
Conversation
The public_agent_messages table requires tenant_id but the RPC function wasn't setting it, causing message saves to fail silently. Now the function gets tenant_id from the current tenant context or falls back to the agent's tenant_id.
|
Caution Review failedThe pull request is closed. 📝 WalkthroughWalkthroughA new PostgreSQL migration adds the Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
📜 Recent review detailsConfiguration used: defaults Review profile: CHILL Plan: Free 📒 Files selected for processing (1)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
The public_agent_messages table requires tenant_id but the RPC function wasn't setting it, causing message saves to fail silently. Now the function gets tenant_id from the current tenant context or falls back to the agent's tenant_id.
Summary by CodeRabbit
Bug Fixes
✏️ Tip: You can customize this high-level summary in your review settings.