Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-30352

Error sorting assignment submissions by comment (in Oracle)

XMLWordPrintable

    • Oracle
    • MOODLE_21_STABLE
    • Hide

      As far as clob datatype isn't allowed in an order by sentence, I suppose that those datatype columns should be casted in allowed datatypes somehow.

      Show
      As far as clob datatype isn't allowed in an order by sentence, I suppose that those datatype columns should be casted in allowed datatypes somehow.
    • Hide

      Sorting assignment submissions by comment shouldn't give any error

      Show
      Sorting assignment submissions by comment shouldn't give any error

      When sorting the assignment submissions by comment it crashes with ORA-00932 inconsistent datatypes: expected - got clob

      * line 394 of \lib\dml\moodle_database.php: dml_read_exception thrown
      * line 268 of \lib\dml\oci_native_moodle_database.php: call to moodle_database->query_end()
      * line 1093 of \lib\dml\oci_native_moodle_database.php: call to oci_native_moodle_database->query_end()
      * line 1325 of \mod\assignment\lib.php: call to oci_native_moodle_database->get_records_sql()
      * line 649 of \mod\assignment\lib.php: call to assignment_base->display_submissions()
      * line 369 of \mod\assignment\type\upload\assignment.class.php: call to assignment_base->submissions()
      * line 57 of \mod\assignment\submissions.php: call to assignment_upload->submissions()

      This is because the comment column (mdl_assignment_submissions.submissioncomment) datatype is CLOB, and that's because (at least in Oracle) that kind of columns aren't allowed in the order by sentence

            moodle.com Moodle HQ
            izendegi Iñigo Zendegi Urzelai
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.