| Summary: | koha-remove needs a --force switch | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Chris Nighswonger <cnighswonger> |
| Component: | Packaging | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | liz, reed, robin |
| Version: | 3.8 | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Crowdfunding goal: | 0 |
| Patch complexity: | --- | Documentation contact: | |
| Documentation submission: | Text to go in the release notes: | ||
| Version(s) released in: | Circulation function: | ||
|
Description
Chris Nighswonger
2012-07-25 02:17:15 UTC
Yes, we definitely should. This bothers me whenever I'm testing the create/remove scripts. I just came up against this - very annoying. Has this already been fixed? The current script seems to already deal with the case of the db not existing. Are there other cases that need coasting over? I think the conditions have been generally improved, this probably isn't necessary any more. |