| 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: | blawlor, dcook, rudy.hinojosa, tomascohen |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | 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
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? |