ref(releases): Add date_added column to release_project table

[cmanallen]

Tracking the date added would be a helpful debugging aid.

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/migrations/0997_add_date_added_to_release_project.py

for 0997_add_date_added_to_release_project in sentry

--
-- Custom state/database change combination
--
ALTER TABLE "sentry_release_project" ADD COLUMN "created_at" timestamp with time zone NULL;

[wedamija]

Any reason to not use date_added here?

[cmanallen]

Conflicts with existing queries which want me to explicitly label the column's origin. Changing the name is a cheap fix way to fix this.

I'm only adding this because it might help me debug customer issues. It has no purpose otherwise. So changing several sections of the code base isn't particularly exciting prospect for me. I may end up closing this pull because if its more trouble than its worth I can operate on less than complete information.

[wedamija]

I don't really understand what you mean here... what code is going to change because you added a new column?

[cmanallen]

We stringly order by COALESCE(date_released, date_added). Where a join to release_project exists the date_added column is ambiguous.

[wedamija]

Ahh, got it... that's annoying. Probably this code can be written in a different way using modern Django so that it's not referencing the sql directly. Anyway, not a huge deal if you want to rename it

[cmanallen]

Sounds good. I don't need this today or even next week. So I may let this pull sit just because.