Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. PO(Yet another) What's the best conversion from an SVN repository to HG repository(ies)?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USRy4an Brase
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO(Yet another) What's the best conversion from an SVN repository to HG repository(ies)?
      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. VTAcceptedByOriginator
    1. COA few thoughts: The first linked answer only addresses part of the problem (have a repository for each project). It says nothing about inter-related projects. The second answer (using subrepos) seems close, but it doesn't quite do it. For example, consider the following: let `nested` be a subrepo for `main`. When I update and commit (and if necessary, push) to `nested`, I need `main` to be able to update and get the changes as well (without the user knowing about the subrepo relationship). However, some testing shows that this isn't the case.
      singulars
      1. PO
      1. USChris Phillips
    2. COAs a follow up on that comment: Specifically, I need changes to the `nested` repository to automatically be made available in the `main` repository. It seems that subrepos only work in the opposite direction (i.e, changes to the subrepo in `main` get promoted/pushed back to the original `nested` repository).
      singulars
      1. PO
      1. USChris Phillips
    3. COsubrepos can go both ways. With subrepos you have a pointer to a specific revision of a subrepo, and you can update that pointer to the tip of the subrepo by just updating in that repo space from within main. It's very much like svn:externals. As a matter of process though, I'd suggest having the subrepo pointer in main track some stable tag in the subrepo, not just the bleeding edge. Even internally having semi-formal product releases is nice, so you can make statement like "outer-project X work with inner-project Y version Z, and if it won't compile with Z+1, just built it against Z".
      singulars
      1. PO
      1. USRy4an Brase
 

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