Ad-hoc database queries

This report plugin allows Administrators to set up arbitrary database queries to act as ad-hoc reports. Reports can be of two types, either run on demand, or scheduled to run automatically. Other users with the right capability can go in and see a list of queries that they have access to. Results can be viewed on-screen or downloaded as CSV.
Price option: Free

Supports Moodle 1.9-5.1 See all versions
Latest release: 2 weeks ago
Installations: 4762
Downloads (last 90 days): 625

Frankenstyle name: report_customsql
Reports

Comments

Comments are no longer open for new posts. Existing comments remain available to read.

The error message is confusing. It should read
Default exception handler: Plugin "report_customsql" is installed in incorrect location "$CFG->dirroot/mod/customsql", expected location is "$CFG->dirroot/report/customsql"
Hello, I tried installing this module and got the following error:
Default exception handler: Plugin "mod_customsql" is installed in incorrect location "$CFG->dirroot/mod/customsql", expected location is "" Debug:
Error code: detectedmisplacedplugin
* line 583 of \lib\upgradelib.php: plugin_misplaced_exception thrown
* line 395 of \lib\upgradelib.php: call to upgrade_plugins_modules()
* line 1584 of \lib\upgradelib.php: call to upgrade_plugins()
* line 431 of \admin\index.php: call to upgrade_noncore()
Fixed version (2.6) now available.
Note that there are some issues with the new version released yesterday. Thanks to those people who reported them, and suggested fixes. I will sort this out tomorrow. In the mean-time I have hidden version 2.5.
OK, I just uploaded a new version, that should be compatible with Moodle 2.4 to 2.6.
The exciting new features is that you can group reports into categories, which helps manage them if you have many.
Is there an official word on 2.6 support?
Hi All
Just wondering if there's any update on the 'side-pre' issue? .. i.e. on 2.5 you click on add new query then you get this error... Coding error detected, it must be fixed by a programmer: Trying to reference an unknown block region side-pre ...
line 884 of /lib/blocklib.php: coding_exception thrown
line 984 of /lib/blocklib.php: call to block_manager->check_region_is_known()
line 997 of /lib/blocklib.php: call to block_manager->ensure_instances_exist()
line 315 of /lib/blocklib.php: call to block_manager->ensure_content_created()
line 1232 of /lib/outputrenderers.php: call to block_manager->get_content_for_region()
line 3053 of /lib/outputrenderers.php: call to core_renderer->blocks_for_region()
line 87 of /theme/stockport/layout/columns2.php: call to core_renderer->blocks()
line 847 of /lib/outputrenderers.php: call to include()
line 777 of /lib/outputrenderers.php: call to core_renderer->render_page_layout()
line 114 of /report/customsql/edit.php: call to core_renderer->header()
Thanks
Andrea
Ok, Tim.
I'll verify there.
Thank you,
hugs!
You would be much better asking for help in the installation forum: https://moodle.org/mod/forum/view.php?id=28. As I say, You don't want to use 2.0. It is terribly old, and does not have things like the report folder.
Hello Tim,
this Moodle version haven't the report folder. Trying create one, but, nothing of different ocurred. Trying to move the plugin for folder /course/report, however, same message of error appeared. The Moodle show another message, telling that the plugin be in wrong folder.
Can you help me?
Thank you!
Ok, Tim! Thank you by help. Following some articles, seems that the best option should be migrate first for 2.0, after, to migrate for 2.x.
What you tell me?
customsql is a Report, not an Activity. Therefore, putting the code in mod/customsql does not work. It needs to go in report/customsql.
Also, 2.0.1 is terribly old. You really should upgrade to 2.6.0.
Dear Tim,
I have updated my moodle 1.9 for 2.0.1, however, some plugins not have been actualized, I need removed then.
I try upload a version 2.0 (or major), but the Moodle show this error:
Plugin "mod_customsql" is defective or outdated, can not continue, sorry.
Thank!
Hugs!!!
No idea. I have never tried Oracle. If you turn on Debugging to DEVELOPER level, and tell us the error message, we might be able to fix it.