ae8223e333
koha-create-defaults substitutes the instance name with the placeholder __KOHASITE__ in the SQL file that it creates. If the instance name is something common, like "data", this means that way too many substitutions will be made, and when koha-create uses the SQL file as a template, broken data can be the result. The solution in this patch was suggested by drojf on IRC. To test: - Create an instance called "data" - Run "sudo koha-dump-defaults data > test.sql" - Take a look at test.sql and verify there are way too many occurences of __KOHASITE__, like "-- Dumping __KOHASITE__ for table `accountlines`" - Apply the patch - Copy the resulting koha-create and koha-dump-defaults to somewhere running off the packages - Run "sudo koha-dump-defaults data > test.sql" again and verify there are only 4 occurrences of __KOHASITE__, in places that make sense - Create an instance with something like: $ gzip test.sql $ sudo koha-create --create-db --defaultsql test.sql.gz test17265 - Verify that you have a working Koha install Signed-off-by: Andreas Roussos <arouss1980@gmail.com> Works as expected. Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> |
||
---|---|---|
.. | ||
koha-create | ||
koha-create-dirs | ||
koha-disable | ||
koha-dump | ||
koha-dump-defaults | ||
koha-email-disable | ||
koha-email-enable | ||
koha-enable | ||
koha-enable-sip | ||
koha-foreach | ||
koha-functions.sh | ||
koha-indexer | ||
koha-list | ||
koha-mysql | ||
koha-mysqlcheck | ||
koha-passwd | ||
koha-plack | ||
koha-rebuild-zebra | ||
koha-remove | ||
koha-reset-passwd | ||
koha-restart-zebra | ||
koha-restore | ||
koha-run-backups | ||
koha-shell | ||
koha-sitemap | ||
koha-start-sip | ||
koha-start-zebra | ||
koha-stop-sip | ||
koha-stop-zebra | ||
koha-translate | ||
koha-upgrade-schema | ||
koha-upgrade-to-3.4 |