-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
fix: User group-by bug #11400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: User group-by bug #11400
Conversation
📝 WalkthroughWalkthroughThe changes add an explicit alias Changes
Sequence Diagram(s)sequenceDiagram
participant Caller
participant AggregationFunction (pg/sqlite3)
participant SQL Engine
Caller->>AggregationFunction (pg/sqlite3): Call replaceDelimitedWithKeyValue*
AggregationFunction (pg/sqlite3)->>AggregationFunction (pg/sqlite3): Construct SQL with subquery alias nc_subquery
AggregationFunction (pg/sqlite3)->>SQL Engine: Execute SQL with aliased subquery
SQL Engine-->>AggregationFunction (pg/sqlite3): Return results
AggregationFunction (pg/sqlite3)-->>Caller: Return results
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
⏰ Context from checks skipped due to timeout of 90000ms (4)
🔇 Additional comments (2)
✨ Finishing Touches
🧪 Generate Unit Tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
75c50ff
to
49b1247
Compare
Change Summary
Provide summary of changes with issue number if any.
Change type
Test/ Verification
Provide summary of changes.
Additional information / screenshots (optional)
Anything for maintainers to be made aware of