Bug 37062

Summary:	REST API endpoint expansion for table saved_sql
Product:	Koha	Reporter:	Rudy Hinojosa <rudy.hinojosa>
Component:	REST API	Assignee:	Bugs List <koha-bugs>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P5 - low	CC:	dcook, rudy.hinojosa, tomascohen
Version:	unspecified
Hardware:	All
OS:	All
Change sponsored?:	---	Patch complexity:	---
Documentation contact:		Documentation submission:
Text to go in the release notes:		Version(s) released in:
Circulation function:

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?