| Summary: | Delete API key or add a deleted flag? | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Jonathan Druart <jonathan.druart> |
| Component: | REST API | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 - low | ||
| 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: | |||
| Bug Depends on: | 20612 | ||
| Bug Blocks: | |||
|
Description
Jonathan Druart
2018-05-08 19:50:11 UTC
(In reply to Tomás Cohen Arazi from comment #23) > (In reply to Jonathan Druart from comment #22) > > Should we really remove a deleted key from the DB table? > > I would flag it as inactive instead, it would permit to keep track of the > > different requests and associate it to a user. > > Disclaimer: This may be a very stupid idea. > > I thought about it too. That would mean an extra column: deleted TINYINT > (1), and it makes sense. |