| Summary: | Use of union in Koha::Objects | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Jonathan Druart <jonathan.druart> |
| Component: | Architecture, internals, and plumbing | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | tomascohen |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20936 | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Attachments: | Bug 25043: Play with union | ||
|
Description
Jonathan Druart
2020-04-02 13:44:37 UTC
Created attachment 102296 [details] [review] Bug 25043: Play with union That will be hard to implement for our Koha::Objects (In reply to Jonathan Druart from comment #2) > That will be hard to implement for our Koha::Objects Speaking about the API use of this to circumvent the current DB issues, I think we can use an approach like this on the (very) few cases in which we have old* tables that might be requested to be included in the resultset. So maybe is not a question of making it a core feature in Koha, but just using in the controllers to compose the result to be sent on the request response. But I am afraid we won't be able to use object.search (In reply to Jonathan Druart from comment #4) > But I am afraid we won't be able to use object.search All the pieces used in objects.search can be used, manually, on the controller method, so that's not a problem. Still valid? |