User:RobertKaye/Schema Change Release May 2012: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
No edit summary
(Adding database schema changes as requested)
Line 12: Line 12:
These tickets appear to be cleanly stated and nearly actionable:
These tickets appear to be cleanly stated and nearly actionable:


* http://tickets.musicbrainz.org/browse/MBS-2885
==== http://tickets.musicbrainz.org/browse/MBS-2885 ====
===== Database changes =====
⚫
* http://tickets.musicbrainz.org/browse/MBS-2851
<pre>
CREATE TABLE iswc
(
id SERIAL,
work INTEGER,
iswc CHARACTER(15),
source SMALLINT,
edits_pending INTEGER,
created TIMESTAMP WITH TIME ZONE
);
ALTER TABLE work DROP COLUMN iswc;
</pre>

* ''TODO'': Clarify constraints, clarify primary key

⚫
==== http://tickets.musicbrainz.org/browse/MBS-2851 ====
===== Database changes =====
<pre>
CREATE TABLE timeline_event (
event_date DATE PRIMARY KEY,
event TEXT NOT NULL,
description TEXT NOT NULL,
link TEXT NOT NULL
);
</pre>

* ''TODO'': Does this belong in the musicbrainz schema?

* http://tickets.musicbrainz.org/browse/MBS-2532
* http://tickets.musicbrainz.org/browse/MBS-2532
* http://tickets.musicbrainz.org/browse/MBS-3788
* http://tickets.musicbrainz.org/browse/MBS-3788

Revision as of 13:17, 27 March 2012

Tickets under consideration for May 15 2012

Conflict tickets

This ticket is a lot of work and may conflict with a Summer of Code proposal:

I'm unsure how to proceed with this ticket.

Clearly stated tickets

These tickets appear to be cleanly stated and nearly actionable:

http://tickets.musicbrainz.org/browse/MBS-2885

Database changes
CREATE TABLE iswc
(
    id             SERIAL,
    work           INTEGER,
    iswc           CHARACTER(15),
    source         SMALLINT,
    edits_pending  INTEGER,
    created        TIMESTAMP WITH TIME ZONE
);
ALTER TABLE work DROP COLUMN iswc;
  • TODO: Clarify constraints, clarify primary key

http://tickets.musicbrainz.org/browse/MBS-2851

Database changes
CREATE TABLE timeline_event (
    event_date DATE PRIMARY KEY,
    event TEXT NOT NULL,
    description TEXT NOT NULL,
    link TEXT NOT NULL
);
  • TODO: Does this belong in the musicbrainz schema?

Next Steps

For each of these tickets, we will require the following two pieces of work:

  • Oliver and Warp will review these tickets and sanity check the proposed schema changes. Due date: 29 March
  • Specify exactly what the user interface changes will be. Mock ups would be great. Due date: 2 April


Tickets that do not provide the required information by the given due date will be removed from the 2012-05-15 schema change.

Retrieved from "https://wiki.musicbrainz.org/index.php?title=User:RobertKaye/Schema_Change_Release_May_2012&oldid=52942"