mirror of
https://github.com/LemmyNet/lemmy.git
synced 2024-05-17 01:12:39 +00:00
9785b20843
* Adding a scaled sort, to boost smaller communities. - Previously referred to as *best* . - Fixes #3622 * Fixing scheduled task update. * Converting hot_rank integers to floats. * Altering hot_rank psql function to default to zero after a week. * Setting scaled_rank to zero, where hot_rank is zero. * Adding image_upload table.
75 lines
2.4 KiB
PL/PgSQL
75 lines
2.4 KiB
PL/PgSQL
-- Change hot ranks and functions from an int to a float
|
|
ALTER TABLE community_aggregates
|
|
ALTER COLUMN hot_rank TYPE float,
|
|
ALTER COLUMN hot_rank SET DEFAULT 0.1728;
|
|
|
|
ALTER TABLE comment_aggregates
|
|
ALTER COLUMN hot_rank TYPE float,
|
|
ALTER COLUMN hot_rank SET DEFAULT 0.1728;
|
|
|
|
ALTER TABLE post_aggregates
|
|
ALTER COLUMN hot_rank TYPE float,
|
|
ALTER COLUMN hot_rank SET DEFAULT 0.1728,
|
|
ALTER COLUMN hot_rank_active TYPE float,
|
|
ALTER COLUMN hot_rank_active SET DEFAULT 0.1728;
|
|
|
|
DROP FUNCTION hot_rank (numeric, published timestamp with time zone);
|
|
|
|
CREATE OR REPLACE FUNCTION hot_rank (score numeric, published timestamp with time zone)
|
|
RETURNS float
|
|
AS $$
|
|
DECLARE
|
|
hours_diff numeric := EXTRACT(EPOCH FROM (now() - published)) / 3600;
|
|
BEGIN
|
|
-- 24 * 7 = 168, so after a week, it will default to 0.
|
|
IF (hours_diff > 0 AND hours_diff < 168) THEN
|
|
RETURN log(greatest (1, score + 3)) / power((hours_diff + 2), 1.8);
|
|
ELSE
|
|
-- if the post is from the future, set hot score to 0. otherwise you can game the post to
|
|
-- always be on top even with only 1 vote by setting it to the future
|
|
RETURN 0.0;
|
|
END IF;
|
|
END;
|
|
$$
|
|
LANGUAGE plpgsql
|
|
IMMUTABLE PARALLEL SAFE;
|
|
|
|
-- The new scaled rank function
|
|
CREATE OR REPLACE FUNCTION scaled_rank (score numeric, published timestamp with time zone, users_active_month numeric)
|
|
RETURNS float
|
|
AS $$
|
|
BEGIN
|
|
-- Add 2 to avoid divide by zero errors
|
|
-- Default for score = 1, active users = 1, and now, is (0.1728 / log(2 + 1)) = 0.3621
|
|
-- There may need to be a scale factor multiplied to users_active_month, to make
|
|
-- the log curve less pronounced. This can be tuned in the future.
|
|
RETURN (hot_rank (score, published) / log(2 + users_active_month));
|
|
END;
|
|
$$
|
|
LANGUAGE plpgsql
|
|
IMMUTABLE PARALLEL SAFE;
|
|
|
|
ALTER TABLE post_aggregates
|
|
ADD COLUMN scaled_rank float NOT NULL DEFAULT 0.3621;
|
|
|
|
UPDATE
|
|
post_aggregates
|
|
SET
|
|
scaled_rank = 0
|
|
WHERE
|
|
hot_rank = 0
|
|
OR hot_rank_active = 0;
|
|
|
|
CREATE INDEX idx_post_aggregates_featured_community_scaled ON post_aggregates (featured_community DESC, scaled_rank DESC, published DESC);
|
|
|
|
CREATE INDEX idx_post_aggregates_featured_local_scaled ON post_aggregates (featured_local DESC, scaled_rank DESC, published DESC);
|
|
|
|
-- We forgot to add the controversial sort type
|
|
ALTER TYPE sort_type_enum
|
|
ADD VALUE 'Controversial';
|
|
|
|
-- Add the Scaled enum
|
|
ALTER TYPE sort_type_enum
|
|
ADD VALUE 'Scaled';
|
|
|