| Summary: | koha-create should check for length of instancename | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Magnus Enger <magnus> |
| Component: | Packaging | Assignee: | Robin Sheat <robin> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Ian Walls <koha.sekjal> |
| Severity: | minor | ||
| Priority: | P5 - low | CC: | mjr, tomascohen |
| Version: | Main | ||
| 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
Magnus Enger
2012-01-09 19:20:43 UTC
I've upgraded this to minor because it seems like a bug rather than an unimplemented feature. I think the fix to bug 6482 offers a way to mitigate this problem. The way I understand bug 6482, it makes it possible to do "koha-create --request-db", change the mysql details in koha-conf.xml and then do "koha-create --populate-db". So it makes it possible to choose a shorter username for mysql if your instancename results in a username that is too long. But there is still a problem for "koha-create --create-db" - since that does everything in one fell swoop. Question: should special measures for the length of the instancename (as described in the description of this bug) only apply to --create-db, or to --request-db as well? (I don't use --request-db (yet) myself, so I don't really have an opinion). |