Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-37350

After conversion SCALE_FACTOR set to null for assignments

    Details

    • Type: Bug
    • Status: Verified
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 12.0, 19.0 [Tentative]
    • Fix Version/s: 12.1, 19.0 [Tentative]
    • Component/s: Assignments
    • Labels:
      None
    • 12 status:
      Resolved
    • Test Plan:
      Hide

      Please add a Test Plan here.

      Show
      Please add a Test Plan here.

      Description

      It seems like after the assignment conversion is run, it's not setting the value of "SCALE_FACTOR" in the database. It should probably either

      • Set the default value when the conversion is run
      • Return the default value from the model if it is null

       

      For people already on 12 I think we can just update them all to their defaults which looks like 100

      SET SQL_SAFE_UPDATES = 0;
      UPDATE ASN_ASSIGNMENT SET SCALE_FACTOR = 10 WHERE SCALE_FACTOR IS NULL;
      SET SQL_SAFE_UPDATES = 1;

       

      You can also update the SCALE_FACTOR to 100 allowing for 2 decimal places with

      SET SQL_SAFE_UPDATES = 0;
      UPDATE ASN_ASSIGNMENT SET SCALE_FACTOR = 100, MAX_GRADE_POINT=MAX_GRADE_POINT * 10 WHERE (SCALE_FACTOR IS NULL OR SCALE_FACTOR = 10);
      SET SQL_SAFE_UPDATES = 1;

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ern Earle R Nietzel
                  Reporter:
                  jonespm Matthew Jones
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code