Normalize the database

[martin.marcher@…]

It would be nice to normalize the database (I'm on postgres for reference)

Currently severities and priorities for example are string values in the ticket table.

It would be easier if they were integers or at least foreign keys with references to a corresponding table.

This would make reports a lot easier as there isn't any (imho) weird construct necessary to sort by severities and priorities. Putting a sample report below.

SELECT p.value AS __color__,
   (CASE owner 
     WHEN '$USER' THEN 'My Tickets' 
     ELSE 'Active Tickets' 
    END) AS __group__,
   id AS ticket, priority, severity, summary, component, t.type AS type, 
   (CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner,
   time AS created,
   changetime AS _changetime, description AS _description,
   reporter AS _reporter

This line (i have to get enum twice with different aliases)

  FROM ticket t, enum p, enum s
  WHERE status IN ('new', 'assigned', 'reopened') AND priority IN ('blocker', 'critical')

These lines (i have to wildly use where to reach the integer values so that I can do a sane comparison)

AND p.name = t.priority AND p.type = 'priority'
AND s.name = t.severity AND s.type = 'severity'

  ORDER BY p.value, s.value, (owner = '$USER') DESC, milestone, t.type, time

[martin.marcher@…]

dunno if this refers to

• #826 which is a possible duplicate of #880
• #4884 which is a duplicate of #4447

so here are at least the ticket id's for your reference. Hope I got the interesting ones for you.

Thanks for the great work people :)

[Remy Blank]

Indeed, this is a duplicate of #826. I'd be surprised if this was ever going to change: much work, high risk, low reward.