Add and change postgresql index when required on DB fields
Registered by
Joël Grand-Guillaume @ camptocamp
Actually, you can add a tag "select=1" or "select="2" on views to say you want to be able to search on that field. But, for both values, no index are created into the database.
This is sometimes boring for some people, and I think we can expect the ORM to handle this properly: Have a look for the number of entries in the table, and if it's needed, add an index on it.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Joël Grand-Guillaume @ camptocamp
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
- Add the parsing of the select placed in views and add indexes if needed
- Nice to have: Create a wizard (or directly into the orm if possible) for performance optimization : it will look into each tables and determines what's the better index to provide for each field, and if it is needed.
(?)
