Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You should definitively use git branches. A possible good git workflow would be this one:</p> <blockquote> <ul> <li>Let's assume that your <strong>Master</strong> branch is currently on Rails 3.0.x and it's in production. </li> <li>From this master branch, you create 2 branches: <strong>rails_30, rails_31.</strong></li> <li>You start working in the <strong>rails_31</strong> branch with all the necessary changes needed for upgrading to Rails 3.1.x (This screencast from Ryan Bates will help you a lot: <a href="http://railscasts.com/episodes/282-upgrading-to-rails-3-1">http://railscasts.com/episodes/282-upgrading-to-rails-3-1</a> )</li> <li>When you are done migrating to Rails 3.1.x (hint: all your tests passing) you can create a new <strong>rails_32</strong> branch from this one. Then you can continue to upgrade to Rails 3.2.x (check out this other railscast: <a href="http://railscasts.com/episodes/318-upgrading-to-rails-3-2">http://railscasts.com/episodes/318-upgrading-to-rails-3-2</a> )</li> <li>When you need to introduce changes to your current Rails 3.0.x code base, you will work on the <strong>rails_30</strong> branch. If a change is good to go and tested, you can push it to master. Once this is pushed you can either try to merge or cherry pick code this branch to your <strong>rails_31</strong> or <strong>rails_32</strong> branch (whichever you are working with at this point in time)</li> </ul> </blockquote> <p><em>Remember that upgrading Rails apps it's not always a trivial task</em>, so take you time &amp; plan accordingly. If you get stucked; a gem is not supported, you logic fails in a newer version of Rails (<em>believe it will most probably happen</em>) Just remember that the Ruby on Rails community is huge, many developers have passed through this before and have share their knowledge in stackoverflow and other sites/blogs. Just keep pushing play.</p> <p><em>Good Luck.</em></p>
    singulars
    1. This table or related slice is empty.
    1. POUpgrade from Rails 3.0 to 3.1 and then to 3.2 - but keep 3.0 working
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAmerico Savinon
    1. USAmerico Savinon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUpgrade from Rails 3.0 to 3.1 and then to 3.2 - but keep 3.0 working
      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. VTAcceptedByOriginator
    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. COThanks, I should have selected the right answer before. Yours and Deradon explanations a good. Yes I ended using branches and so far compatibility has been ok.
      singulars
      1. PO
      1. USPod
 

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