Bug 37062 - REST API endpoint expansion for table saved_sql
Summary: REST API endpoint expansion for table saved_sql
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: REST API (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-10 14:52 UTC by Rudy Hinojosa
Modified: 2024-06-11 04:12 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rudy Hinojosa 2024-06-10 14:52:04 UTC
I'd like to request a CRUD endpoint expansion for table saved_sql. I'm working on a report project that would greatly enhance the end user experience for robust reporting through Jasper. My project is called Koha-Jasper 

This program will allow a user to import a custom report PAK and automatically build a report for the end user via an API call. 

I'm currently using a direct sql call, but I don't want this to be the standard way to communicate to the table.

More information on this project: https://lightwavelibrary.com/jasper/
Comment 1 David Cook 2024-06-11 04:12:16 UTC
A CRUD endpoint for managing the table saved_sql shouldn't be a drama.

However, I imagine that you're also talking about an endpoint that returns the output of saved queries? That sounds like it would have a number of security concerns. 

Why not continue with the approach of just downloading CSV from Koha and using that as the data source for your Jasper reports?