This is a snapshot of Indico's old Trac site. Any information contained herein is most probably outdated. Access our new GitHub site here.

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#454 closed enhancement (fixed)

Update Recording Manager monitoring database queries

Reported by: jherr Owned by: jherr
Priority: normal Milestone: v0.97.0
Component: Video Services Version: 0.97.0
Keywords: Recording Manager Cc:

Description

Some field names have changed in the micala monitoring database to make them more readable

Change History (5)

comment:1 Changed 5 years ago by jherr

  • Status changed from new to accepted

comment:2 Changed 5 years ago by Jose Benito <jose.benito.gonzalez@…>

In [336d4ec92ed8098e89658f882e7b5fbde90516c1]:

[IMP] changes to micala DB queries

  • adjusted DB queries according to recent field name changes (Lectures.id -> Lectures.idLecture, Machines.id -> idMachine, etc)
  • Found a bug where cds_indico_pending was being built incorrectly. I was taking the set difference between the set of IndicoID's for which the CDS export task was started and the set of IndicoID's for which a CDS record currently actually exists, but I should have been using the set of IndicoID's for which the task was marked as COMPLETE in the database. cds_indico_pending is now the set of what the micala database knows as pending, not what is actually pending. After getCDSPending() is called, we update the micala DB with the very latest changes in updateMicalaCDSExport().
  • Shortened some SELECT queries by using a newly created MySQL view called ViewStatusComprehensive?, so I don't have to do a big join in the code.
  • fixes #454

comment:3 Changed 5 years ago by jbenito

  • Resolution set to fixed
  • Status changed from accepted to closed

comment:4 Changed 5 years ago by Jeremy Herr <jeremy.herr@…>

In [336d4ec92ed8098e89658f882e7b5fbde90516c1]:

[IMP] changes to micala DB queries

  • adjusted DB queries according to recent field name changes (Lectures.id -> Lectures.idLecture, Machines.id -> idMachine, etc)
  • Found a bug where cds_indico_pending was being built incorrectly. I was taking the set difference between the set of IndicoID's for which the CDS export task was started and the set of IndicoID's for which a CDS record currently actually exists, but I should have been using the set of IndicoID's for which the task was marked as COMPLETE in the database. cds_indico_pending is now the set of what the micala database knows as pending, not what is actually pending. After getCDSPending() is called, we update the micala DB with the very latest changes in updateMicalaCDSExport().
  • Shortened some SELECT queries by using a newly created MySQL view called ViewStatusComprehensive?, so I don't have to do a big join in the code.
  • fixes #454

comment:5 Changed 5 years ago by Jeremy Herr <jeremy.herr@…>

In [336d4ec92ed8098e89658f882e7b5fbde90516c1]:

[IMP] changes to micala DB queries

  • adjusted DB queries according to recent field name changes (Lectures.id -> Lectures.idLecture, Machines.id -> idMachine, etc)
  • Found a bug where cds_indico_pending was being built incorrectly. I was taking the set difference between the set of IndicoID's for which the CDS export task was started and the set of IndicoID's for which a CDS record currently actually exists, but I should have been using the set of IndicoID's for which the task was marked as COMPLETE in the database. cds_indico_pending is now the set of what the micala database knows as pending, not what is actually pending. After getCDSPending() is called, we update the micala DB with the very latest changes in updateMicalaCDSExport().
  • Shortened some SELECT queries by using a newly created MySQL view called ViewStatusComprehensive?, so I don't have to do a big join in the code.
  • fixes #454
Note: See TracTickets for help on using tickets.