Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here are three ways to do this. I'll discuss the pros and cons of each:</p> <p><strong>Option 1</strong>: use <code>hg diff</code> to get a diff file showing the uncommited changes, and then <code>hg import --nocommit</code> on the receiving end to apply those changes without creating a new changeset</p> <ul> <li><strong>Pros</strong>: simple, creates no changesets</li> <li><strong>Cons</strong>: doesn't actually use mercurial ike the DVCS it is. Might not catch newly added files</li> </ul> <p><strong>Option 2</strong>: Commit on the sending side, push to the receiving end (or pull from it, or put a <code>hg bundle</code> on a flash drive), bypassing the work server, <code>update</code> on the receiving side, and then <code>hg rollback</code> on <strong>both</strong> sides to eliminate the changeset (but leave the changes.</p> <ul> <li><strong>Pros</strong>: Using push and pull to move over changes like mercurial intends</li> <li><strong>Cons</strong>: Hacky. Relies on rollback which only works 1-level deep. Accidentally pull twice and you can't undo the first.</li> </ul> <p><strong>Option 3</strong>: Commit on the sending side. Push to a developer-repo that only you access, and Pull on the receiving end. Don't push to the company repo until things build, but when you do push push all the interstitial changesets</p> <ul> <li><strong>Pros</strong>: Exactly what a DVCS is about. Your order of work is documented and preserved</li> <li><strong>Cons</strong>: requires setting up a you-only clone</li> </ul> <p>FWIW, I recommend option 3. Per-developer repositories are exactly what DVCSs are about. If your company doesn't make it easy to set one up on a server you can access from home and away, point out to them the immense value in having documented the process that got a developer to a completed fix/feature <strong>and</strong> that encouraging developers to push to a not-required-to-compile repo frequently is good for daily backups.</p> <p>Lastly, after you're done with your feature or fix you can always collapse-away all the intermediary changesets. I don't like do it (I'm a <em>show your work</em> kind of guy), but here's how: <a href="https://stackoverflow.com/questions/1725607/can-i-squash-commits-in-mercurial/1725638#1725638">Can I squash commits in Mercurial?</a></p>
    singulars
    1. This table or related slice is empty.
    1. POMoving incomplete code between mercurial checkouts
      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. POMoving incomplete code between mercurial checkouts
      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. VTAcceptedByOriginator
    1. COoption 4, for advanced user: share a mq queue
      singulars
      1. PO
      1. UStonfa
    2. COExactly the kind of answer I was looking for. Will be option 3 then, since I have already setup my own repository. I was just struggling a bit with the thought of having broken (uncompiling) changesets in my history. And I dont think collapsing changesets is a good idea, since the repository is public (in the way that I havent tried to make it hidden) someone *may* have cloned it, hence I should leave the history intact.
      singulars
      1. PO
      1. USMizipzor
    3. COmizipzor, I think you're making the right choice. Rewriting history always feels sleezy to me even though it's a totally valid work mode. Sort of feels like doing science in pencil instead of pen.
      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