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

Oracle SQL Statement problem -- unable to list glossary entries

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • 1.8.4, 1.9, 2.0
    • 1.8.2
    • Glossary
    • None
    • Red Hat Enterprise Linux ES release 4 (Nahant Update 5)
      PHP Version 5.2.3
      Oracle Database 10g Release 10.2.0.1.0
    • Oracle
    • MOODLE_18_STABLE
    • MOODLE_18_STABLE, MOODLE_19_STABLE, MOODLE_20_STABLE
    • sorry, intranet :)

      While trying to use the auto-linking functionality with the glossary, I got nothing.....
      When looking into code, I found a bug ; it seems to be relative to Oracle
      The clause: != \'\' appears to not working under my Oracle....???
      And obviously is not null does (but does not test the same).

      Another problem shows up after it, when having aliases without entries or categories, the array_merge with a null array fails !

      I've modified this in the joined file. Here's the diff lines:
      73,74c73,74
      < AND ge.concept != \'\' ');
      <

      > AND ge.concept is not null '); //Joseph Boiteau: previous sql isn't working with Oracle
      > // and moreover, the string could'nt be emptyl using interface
      85c85,86
      < if ($aliases) {

      > // Joseph Boiteau: adding controls to not use a null $concepts object
      > if ($aliases and $concepts) {
      87a89,91
      > elseif ($aliases)

      { > $concepts = $aliases; > }

      Should I commit that somewhere ?
      Is it a bad sql or an Oracle abnormal comportment ?

      It's working here but I don't know what to do with that !

            stronk7 Eloy Lafuente (stronk7)
            jobano Joseph Boiteau
            Nobody Nobody
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

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