View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005740 | Composr | core_database_drivers | public | 2024-04-28 18:41 | 2024-07-25 22:17 |
| Reporter | Patrick Schmalstig | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0005740: Analyse use of fields in database for possible optimisation | ||||
| Description | It may be possible to optimise some of the fields using the integer database type to use one that requires less bytes (e.g. smallint / mediumint). Have a look through the schema to see if this can be done anywhere. Exclude ID numbers because we are already planning to switch to GUIDs for those in v12. Possible to use hash-specific types on hash columns. For example, we could create a Composr type HASH_MD5 for MD5 hashes which translates to char(32) or binary(16). Or HASH_BCRYPT for CHAR(60) / BINARY(60). Or just HASH for our commonly-used 13-character hex hashes CHAR(13) / BINARY(7). | ||||
| Tags | Roadmap: Over the horizon | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
| related to | 0005546 | non-assigned | cms_stats table takes too much space |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-04-28 18:41 | Patrick Schmalstig | New Issue | |
| 2024-04-28 19:17 | Patrick Schmalstig | Tag Attached: Roadmap: Over the horizon | |
| 2024-07-23 17:10 | Patrick Schmalstig | Relationship added | related to 0005546 |
| 2024-07-25 22:17 | Chris Graham | Severity | Trivial-bug => Feature-request |
