Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you want to move the repository and keep history, you'll probably need filesystem access on both hosts. The simplest solution, if your backend is FSFS (the default on recent versions), is to make a filesystem copy of the entire repository folder.</p> <p>If you have a Berkley DB backend, if you're not sure of what your backend is, or if you're changing SVN version numbers, you're going to want to use svnadmin to dump your old repository and load it into your new repository. Using <code>svnadmin dump</code> will give you a single file backup that you can copy to the new system. Then you can create the new (empty) repository and use <code>svnadmin load</code>, which will essentially replay all the commits along with its metadata (author, timestamp, etc).</p> <p>You can read more about the dump/load process here:</p> <p><a href="http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate" rel="noreferrer">http://svnbook.red-bean.com/en/1.8/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate</a></p> <p>Also, if you do <code>svnadmin load</code>, make sure you use the <code>--force-uuid</code> option, or otherwise people are going to have problems switching to the new repository. Subversion uses a UUID to identify the repository internally, and it won't let you switch a working copy to a different repository.</p> <p>If you don't have filesystem access, there may be other third party options out there (or you can write something) to help you migrate: essentially you'd have to use the svn log to replay each revision on the new repository, and then fix up the metadata afterwards. You'll need the pre-revprop-change and post-revprop-change hook scripts in place to do this, which sort of assumes filesystem access, so YMMV. Or, if you don't want to keep the history, you can use your working copy to import into the new repository. But hopefully this isn't the case.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I export (and then import) a Subversion repository?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USbahrep
    1. USTadmas
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do I export (and then import) a Subversion repository?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSince 1.7, you can now svnrdump, which doesn't require admin rights on the remote repos. Command is easy: `svnrdump dump https//remote/svn/trunk > repos.dump`. In most cases, the command works with SVN 1.6 as well, but may have some issues, see docs. Works both in *nix and Windows.
      singulars
      1. PO
      1. USAbel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload