Skip to content

Remove usage of `user_interacted_projects` table

What does this MR do and why?

First step of #360823 (closed).

In #360823 (closed), we noted that the user_interacted_projects table is not being used in the app anymore (for reads). This table is being written into currently, but that data is not being read anywhere - which makes this table redundant.

This table can be dropped, as per the conversation in #360823 (comment 1600117812).

However, before this table can be dropped, the first step is to stop writes to this table, which is currently happening via a callback.

Along with this, this MR also removes the model classes and associations related with this table.

Once this is merged, in the next milestone, this table is safe to be dropped.

More context is in !137791 (comment 1664920444)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #360823 (closed)

Edited by Manoj M J

Merge request reports