Introduce a pm_thread table

Created on 16 March 2010, about 15 years ago
Updated 24 April 2025, 13 days ago

I am really tired banging my head at the absent pm_thread table. It makes Views integration big pain. I suggest to make following changes:
1) Create "pm_thread" table with columns containing thread properties, which currently are calculated by aggregate queries.
2) Move thread subject (which is really a thread property, not a message property) from "pm_message" to "pm_thread". Maybe move something else too.
3) Update "pm_thread" on every pm_message and pm_index change. Wrap the whole action (including hook invocation) in transaction. Do not run aggregated queries but instead query pm_thread directly.
Please let me know what do you think about it, cause that sounds like it's easier to rewrite it from the scratch :-/

Feature request
Status

Closed: outdated

Version

2.0

Component

Code

Created by

🇷🇺Russia crea

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024