Ticket #1037 (closed enhancement: wontfix)

Opened 3 years ago

Last modified 11 months ago

Refactor builds/build_requests tables to remove duplicate rows in builds table.

Reported by: catlee Owned by:
Priority: minor Milestone: 0.8.7
Version: 0.8.1 Keywords: database
Cc:

Description

If you have a build that has merged more than one build request, you'll have one row in the builds table per build request. Each row will be identical, except for the column linking back to the build request.

This makes writing tools a bit complicated since you have to cope with the fact that more than one row in builds can correspond to the same single build on a slave.

I think we need another table that maps builds to build requests, e.g. a list of (build request id, build id) tuples. We could then drop the 'brid' column from the builds table.

Change History

comment:1 Changed 3 years ago by dustin

  • Keywords database added

comment:2 Changed 2 years ago by dustin

  • Milestone changed from 0.8.3 to 0.8.4

This refactor should wait until sqlalchemy has landed in 0.8.4

comment:3 Changed 2 years ago by dustin

  • Milestone changed from 0.8.4 to 0.8.5

schema change -> 0.8.5

comment:4 Changed 11 months ago by dustin

  • Status changed from new to closed
  • Resolution set to wontfix

The builds table will get dropped when builds actually move into the database, so I don't want to try do do anything in the interim.

Note: See TracTickets for help on using tickets.