Revert "fix: Patched SQL dialect issue LIMIT vs TOP in favor of Microsoft SQL Server (#101)"

This reverts commit 2fa7dc6.

The solution to the SQL dialect issue is suboptimal. Moodle’s datalib
provides the right means of abstraction to formulate our query without
database-specific code. We can use the parameter $limitnum from the
method get_records_sql of the class moodle_database.

Author: dlmsr

classes/review.php

@@ -107,20 +107,12 @@ public static function get_first_review_post($moodleoverflowid, $afterpostid = n
             $addwhere = ' AND p.id != :notpostid ';
             $params['notpostid'] = $afterpostid;
         }
-        /* Handle different SQL dialects in favor of Microsoft SQL Server */
-        if (is_a($DB, 'sqlsrv_native_moodle_database')) {
-            $top = 'TOP 1';
-            $limit = '';
-        } else {
-            $top = '';
-            $limit = 'LIMIT 1';
-        }
         $record = $DB->get_record_sql(
-            "SELECT $top p.id as postid, p.discussion as discussionid FROM {moodleoverflow_posts} p " .
+            'SELECT p.id as postid, p.discussion as discussionid FROM {moodleoverflow_posts} p ' .
             'JOIN {moodleoverflow_discussions} d ON d.id = p.discussion ' .
             "WHERE p.reviewed = 0 AND d.moodleoverflow = :moodleoverflowid AND p.created < :reviewtime $addwhere " .
             "ORDER BY $orderby p.discussion, p.id " .
-            $limit,
+            'LIMIT 1',
             $params
         );
         if ($record) {