epriestley 924b135d31 Add a storage renamespace for mangling SQL dumpfiles into a new namespace ... Summary: Ref T7149. When users give us dumpfiles for import, they will almost inevitably use the `phabricator` namespace. They need to be renamed to use an instance namespace. We can do this either by: - importing the data first, then renaming; or - renaming first, then importing. This implements the second one, basically `storage renamespace --in dump.sql --from phabricator --to instancename > instance.sql`. Renaming first is a little hackier since we have to `preg_match()` a SQL dump file, but I think it's better overall: - With only one database, it lets you dump/import without downtime. - If you have development stuff in a development environment in the `phabricator` namespace, you don't have to move it aside to do an import. - No possibility that two people doing an import at the same time on the same box will collide with each other. - You can do the rename once and then repeat the import process with the renamed dump more easily. - No tricky stuff with modern Phabricator running against an old dump and the database names not matching up. None of this is super important, but it just makes large dumps a bit easier to work with, and the dumpfile format is regular enough that this seems unlikely to ever really not work. Test Plan: Renamespaced a dump, did a `diff -u`, saw all the relevant parts changed (and only those parts changed). Reviewers: btrahan Reviewed By: btrahan Subscribers: epriestley Maniphest Tasks: T7149 Differential Revision: https://secure.phabricator.com/D12105		2015-03-17 18:29:01 -07:00
..
workflow	Add a storage renamespace for mangling SQL dumpfiles into a new namespace	2015-03-17 18:29:01 -07:00
PhabricatorStorageManagementAPI.php	Fix quickstart.sql for old MySQL	2015-03-02 09:57:38 -08:00
PhabricatorStoragePatch.php	Mark dead databases as "dead" and don't dump, probe, or list them	2013-07-19 11:07:29 -07:00