Esko Arajärvi
25bb9b12c1
Faster count queries when updating the info about current node
...
MySQL optimiser seems to prefer a full table scan of `post-user`
table in the count query mentioned in issue #14763 . When the origin
and deleted columns are added to the index, the IN-query part of
the query can be done with index-only scan, which is much faster.
Adding the columns in the order
uri-id, origin, deleted
allows some other queries to also use it when checking
for uri-id and origin.
Fixes #14763
2025-02-04 19:47:31 +02:00
Michael
2eadad49db
Fetch replies to fetched posts
2024-06-26 08:33:07 +00:00
Michael
7a0c5d141e
Issue 13714: Support for "commentsEnabled" and "capabilities"
2024-03-21 17:11:20 +00:00
Michael
1cd729531d
Sorting changed to "created"
2023-12-14 06:18:17 +00:00
Michael
eae1affb21
Index added
2023-12-14 05:36:31 +00:00
Michael
ca8a89ed1c
Use reshare with Diaspora like with ActivityPub
2022-12-13 23:19:19 +00:00
Michael
3e2c684319
Some more index / fatal erros fixed
2022-08-16 11:23:47 +00:00
Michael
7106106f11
Formatted index list
2021-06-14 12:15:10 +00:00
Michael
3d74d0a49c
Updated documentation
2021-06-14 08:54:57 +00:00
Michael
96f07c7288
Indexes and foreign keys added
2021-06-14 08:53:37 +00:00
Michael
2cd0c1d30d
Trailing whitespace removed
2021-06-14 06:10:11 +00:00
Michael
fd30df7300
Pad the header
2021-06-14 05:58:51 +00:00
Michael
4095e6c9be
Pad the lengths of the columns
2021-06-14 05:33:47 +00:00
Michael
a827f948c8
Reversed "null"
2021-06-14 05:14:09 +00:00
Michael
31db9dbef7
Added default value "NULL"
2021-06-14 05:08:01 +00:00
Michael
84ab5d6159
Updates database structure documentation
2021-06-13 20:33:50 +00:00