Databases
StackOverflow2013
Postsdbo
POUse of Migrations in Ruby on Rails
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUse of Migrations in Ruby on Rails
    primarykey
    data
    text
    <p>I would like to confirm that the following analysis is correct:</p> <p>I am building a web app in RoR. I have a data structure for my postgres db designed (around 70 tables; this design may need changes and additions during development to reflect Rails ways of doing things. EG, I designed some user and role tables - but if it makes sense to use Restful Authentication, I will scrub them and replace with whatever RA requires. ).</p> <p>I have a shellscript which calls a series of .sql files to populate the empty database with tables and initial data (eg, Towns gets pre-filled with post towns) as well as test data (eg, Companies gets a few dummy companies so I have data to play with). </p> <p>for example:</p> <pre><code>CREATE TABLE towns ( id integer PRIMARY KEY DEFAULT nextval ('towns_seq'), county_id integer REFERENCES counties ON DELETE RESTRICT ON UPDATE CASCADE, country_id integer REFERENCES countries ON DELETE RESTRICT ON UPDATE CASCADE NOT NULL, name text NOT NULL UNIQUE ); </code></pre> <p>Proposition 0: Data lasts longer than apps, so I am convinced that I want referential integrity enforced at the DB level as well as validations in my RoR models, despite the lack of DRYNESS.</p> <p>Proposition 1: If I replace the script and sql files with Migrations, it is currently impossible to tell my Postgres database about the Foreign Key and other constraints I currently set in SQL DDL files within the migration code. </p> <p>Proposition 2: The touted benefit of migrations is that changes to the schema are versioned along with the RoR model code. But if I keep my scripts and .sql files in railsapp/db, I can version them just as easily.</p> <p>Proposition 3: Given that migrations lack functionality I want, and provide benefits I can replicate, there is little reason for me to consider using them. So I should --skipmigrations at script/generate model time. </p> <p>My question: If Proposition 0 is accepted, are Propositions 1,2,3 true or false, and why?</p> <p>Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJames A. Rosen
    1. USNickR
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUse of Migrations in Ruby on Rails
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUse of Migrations in Ruby on Rails
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUse of Migrations in Ruby on Rails
      1. USMike Berrow
      1. VTFavorite
    1. COCode formatting: Just use 4 spaces before each code line. StackOverflow will treat it as a pre-formatted block (incl. indentation) and most of the time will pick the right syntax highlighting for it.
      singulars
      1. POUse of Migrations in Ruby on Rails
      1. USwebmat
    2. COThere ya go, @webmat.
      singulars
      1. POUse of Migrations in Ruby on Rails
      1. USJames A. Rosen
 

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