-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
[ROMM-994] Autogenerated collections #1562
Conversation
array_to_json(array_agg(rom_id)) as rom_ids, | ||
array_to_json(array_agg(path_cover_s)) as path_covers_s, | ||
array_to_json(array_agg(path_cover_l)) as path_covers_l |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This differs from MySQL, where we use DISTINCT
within the aggregation. I don't think that's needed as I don't see a way for CTEs to repeat rom_id
values. We should have the same logic for both engines.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i can't seem to figure out how to DISTINCT
in postgres like i did in mysql 🤷🏼
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Description
Very excited about this one! This PR creates a virtual database table that collects and groups games based on certain IGDB metadata fields: collections, franchises, genres, companies and modes. The list of virtual
VirtualCollections
can be fetched and filtered by type, and displayed in the home screen and collections sidebar. Editing these virtual collections is not possible, so controls like the collection editor window are hidden.As we add more metadata providers, we can update the virtual table to pull properties outside
igdb_metadata
.TODO
Related Issues
Closes #994
Checklist
Please check all that apply.
Screenshots