Change Details

I noticed that for redirects, for example, there are rows in the database for category count, citation count, and even AfC state. This information is not exposed in the interface for redirects because they aren't applicable, hence we probably shouldn't store them in the first place. Similarly drafts and user pages shouldn't have category count, etc. It is worth noting that the values for these specific tags are small integers, but they are stored as a VARBINARY (`ptrpt_value`).

I noticed that for redirects, for example, there are rows in the `pagetriage_page_tags` table for category count, citation count, and even AfC state. This information is not exposed in the interface for redirects because they aren't applicable, hence we probably shouldn't store them in the first place. Similarly drafts and user pages shouldn't have category count, etc. It is worth noting that the values for these specific tags are small integers, but they are stored as a VARBINARY (`ptrpt_value`).

I noticed that for redirects, for example, there are rows in the databas`pagetriage_page_tags` table for category count, citation count, and even AfC state. This information is not exposed in the interface for redirects because they aren't applicable, hence we probably shouldn't store them in the first place. Similarly drafts and user pages shouldn't have category count, etc. It is worth noting that the values for these specific tags are small integers, but they are stored as a VARBINARY (`ptrpt_value`).