Fix SQL error in GetClipsQualifyingForRemoval

[isZumpo]

This commit removed a important n from the SQL statement. Causing unit tests etc to fail:

Since the original commit got merged quite quickly, so did a small hack I used to get in a AS n. This pull request fixes that hack by doing it the way gorm intended for it to be done.

Summary by CodeRabbit

• Refactor
  • Improved the query logic for identifying clips eligible for removal based on retention policies, enhancing performance and accuracy.

[coderabbitai]

Walkthrough

The update involves refining the query mechanism in the DataStore struct, specifically the GetClipsQualifyingForRemoval method. A subquery is now strategically utilized as a table within the main query to enhance the selection process of clips for removal, aligning with the defined retention policy.

Changes

File Path	Change Summary
internal/.../interfaces.go	Updated the GetClipsQualifyingForRemoval method in the DataStore struct to include a subquery used as a table in the main query for better targeting of clips based on retention policy.

🐇✨
In the realm of code, where queries intertwine,
A clever little update, oh so fine!
Subqueries dance, in tables they weave,
Finding old clips that we no longer need.
Hop, skip, a jump! Clean-up's a delight,
With smarter queries taking flight. 🚀
🐰💻

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between cb99a02 and 9904eba.

Files selected for processing (1)

• internal/datastore/interfaces.go (1 hunks)

Additional comments not posted (2)

internal/datastore/interfaces.go (2)

217-217: Ensure the subquery alias is correctly referenced in the main query.

The subquery is aliased as n, but it's not clear if this alias is consistently used in the joins and selections. Please verify that all references to fields in the subquery correctly use the n alias.

---

217-217: The revised SQL query construction appears to align with the intended improvements.

This change should correctly handle the integration of the subquery as a table, which is crucial for the functionality of identifying clips for removal. Good job on addressing the previous error effectively.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.