Ticket #1053 (new enhancement)

Opened 3 years ago

Last modified 4 months ago

schedulerdb should have id columns on all tables

Reported by: Pike Owned by:
Priority: major Milestone: 0.9.0
Version: 0.8.2 Keywords: database, sprint
Cc: l10n.moz@…, kshriram18@…

Description (last modified by dustin) (diff)

I've been hacking on a django wrapper on the schedulerdb, and django really wants id columns on all tables.

The list of affected tables seems to be 

buildset_properties
change_files
change_links
change_properties
last_access
scheduler_changes
scheduler_upstream_buildsets
sourcestamp_changes
version

Change History

comment:1 Changed 3 years ago by dustin

  • Keywords database added
  • Type changed from undecided to enhancement
  • Description modified (diff)
  • Milestone changed from undecided to 0.8.3

The version table is a singleton (soon to be replaced with migrate_version).

I don't see what harm an extra column will do in the other tables. I'll take care of this when the SQLAlchemy stuff lands.

Thanks, Axel!

comment:2 Changed 3 years ago by Pike

  • Cc l10n.moz@… added

comment:3 Changed 2 years ago by dustin

  • Milestone changed from 0.8.3 to 0.8.4

sqlalchemy will land in 0.8.4.

comment:4 Changed 2 years ago by dustin

  • Milestone changed from 0.8.4 to 0.8.5

schema change -> 0.8.5

comment:5 Changed 14 months ago by dustin

  • Keywords database, sprint added; database removed

comment:6 Changed 8 months ago by dustin

  • Milestone changed from 0.8.+ to 0.9.0

comment:7 Changed 7 months ago by Dustin J. Mitchell

add id columns for new many-to-many table

Refs #1053.

Changeset: d36391c79639afc76919f50135313bc2017a283d

comment:9 Changed 4 months ago by ShriramK

  • Cc kshriram18@… added
Note: See TracTickets for help on using tickets.