Repository navigation
Add more indexes to database #709
Copy link
Copy link
Open
Labels
databaseDatabase-related: SQL, AR, migrations, etcDatabase-related: SQL, AR, migrations, etcgood first issueThis issue should be suitable for less experienced developersThis issue should be suitable for less experienced developershelp offeredI would be very happy to help less experienced developers tackle this issue (advice/pairing/etc)I would be very happy to help less experienced developers tackle this issue (advice/pairing/etc)main appDEPRECATED: main_app before the core plugin refactor (was: 'core' stuff that isn't in plugins)DEPRECATED: main_app before the core plugin refactor (was: 'core' stuff that isn't in plugins)pluginDEPRECATED: split into core/features/support (was: about a plugin or the code that supports them)DEPRECATED: split into core/features/support (was: about a plugin or the code that supports them)
Description
There are probably quite a few places where the database could benefit from having more indexes added.
As a rule of thumb, I think there should be an index on any column that is used in a scope or a utility method to filter the contents of the table down to a smaller result-set (e.g. posted_at for .recent), as well as any column that gets used for single-row lookups (e.g. slugs).
Relatedly; I think there are already indexes on all the foreign keys, but it wouldn't hurt to check and make sure - particularly for things like page->elements, group->memberships, etc.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
databaseDatabase-related: SQL, AR, migrations, etcDatabase-related: SQL, AR, migrations, etcgood first issueThis issue should be suitable for less experienced developersThis issue should be suitable for less experienced developershelp offeredI would be very happy to help less experienced developers tackle this issue (advice/pairing/etc)I would be very happy to help less experienced developers tackle this issue (advice/pairing/etc)main appDEPRECATED: main_app before the core plugin refactor (was: 'core' stuff that isn't in plugins)DEPRECATED: main_app before the core plugin refactor (was: 'core' stuff that isn't in plugins)pluginDEPRECATED: split into core/features/support (was: about a plugin or the code that supports them)DEPRECATED: split into core/features/support (was: about a plugin or the code that supports them)
Activity
denny commentedon Nov 12, 2020
If you are a less experienced developer who is looking at this issue and thinking you'd like to try to take it on but you're not entirely confident, I would be happy to help you - whether that's help getting set up, more explanation of what needs doing, pairing on the code task itself, or anything else I can do to help.
In my day job I'm a lead developer who often mentors less experienced developers, and I'd love to use some of that experience to help people take their first steps into contributing to open source projects.