Confirm InnoDB secondary index structure for comments table

[Copilot]

Review comment questioned whether comment_id (PK) should be explicitly included in the composite index (post_id, parent_id) for the comments table, given queries that filter and sort by these columns.

Analysis

InnoDB secondary indexes automatically include the primary key in leaf nodes. The index defined as:

CREATE INDEX idx_comments_post_parent ON comments (post_id, parent_id);

Internally functions as (post_id, parent_id, comment_id). Queries like:

WHERE post_id=? AND parent_id IS NULL ORDER BY comment_id DESC

Already use the index efficiently for both filtering and sorting without explicit PK inclusion.

Outcome

• Current implementation is optimal
• No changes required to migration or entity annotations
• Explicit comment_id inclusion would be redundant (no performance impact either way)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/graphql
  • Triggering command: /usr/bin/gh gh pr view 346 --json title,body (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)