Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your development database is being purged because ActiveRecord::Base.configurations has the test database set to "development.sqlite3". When the rake task is run, the yaml configuration is eval'ed into the ActiveRecord::Base.configurations hash and at that time Rails.env is set to development.</p> <p>If RAILS_ENV=development, the database value for test will be set to</p> <pre><code>database: db/development.sqlite3 </code></pre> <p>or for a different adapter:</p> <pre><code>database: my_app_development </code></pre> <p>You can reproduce this with a simple sqlite only configuration buy changing the test block inside database.yml to the following:</p> <pre><code>test: adapter: sqlite3 database: db/&lt;%= Rails.env %&gt;.sqlite3 pool: 5 timeout: 5000 </code></pre> <p>If you inspect the full ActiveRecord::Base.configurations hash you'll see that test is set to use the development db if no RAILS_ENV is specified. And if you were to specify 'production' or 'staging' it would be set to that. From the console:</p> <pre><code># rails c &gt; ActiveRecord::Base.configurations['test']['database'] =&gt; "db/development.sqlite3" </code></pre> <p>compared with:</p> <pre><code># RAILS_ENV=test rails c &gt; ActiveRecord::Base.configurations['test']['database'] =&gt; "db/test.sqlite3" </code></pre> <p><strong>Update</strong></p> <p>The issue you are seeing with db:reset is also because your yaml file is interpreted once and then the config is set.</p> <p>db:reset will invoke db:drop and db:setup for the given environment. However, if the environment is development, it also does those tasks for the test environment. So it succeeds in dropping for the development environment and then when it executes for test, the database key of the configuration is identical to the development section, hence it can't drop something that no longer exists. Here is what the ActiveRecord::Base.configurations hash looks like when Rails.env == 'development'</p> <pre><code>"development" =&gt; { "adapter" =&gt; "sqlite3", "database" =&gt; "db/development.sqlite3", "pool" =&gt; 5, "timeout" =&gt; 5000 }, "test" =&gt; { "adapter" =&gt; "sqlite3", "database" =&gt; "db/development.sqlite3", "pool" =&gt;5, "timeout"=&gt;5000 }, "production" =&gt; { "adapter" =&gt; "sqlite3", "database" =&gt; "db/development.sqlite3", "pool"=&gt;5, "timeout"=&gt;5000 } </code></pre> <p>And once it's in that hash, it doesn't go back and re-read the database.yml file. That hash is what is generated given this <strong>database.yml</strong></p> <pre><code>development: adapter: sqlite3 database: db/&lt;%= Rails.env %&gt;.sqlite3 pool: 5 timeout: 5000 test: adapter: sqlite3 database: db/&lt;%= Rails.env %&gt;.sqlite3 pool: 5 timeout: 5000 production: adapter: sqlite3 database: db/&lt;%= Rails.env %&gt;.sqlite3 pool: 5 timeout: 5000 </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PORake db:test:prepare task deleting data in development database
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLukas Eklund
    1. USLukas Eklund
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORake db:test:prepare task deleting data in development database
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COThanks very much for this detailed answer. It prompted me to go and have another look around Google and StackOverflow for [ways to override `rake` tasks](http://stackoverflow.com/q/8112074/567863) to see if I could [force the environment to `test`](http://stackoverflow.com/q/1090176/567863). Doesn't seem easy to do with a task like `db:test:prepare` which [only cares about grabbing the test db info and not about what environment it's in](http://stackoverflow.com/a/5527051/567863), so for reasons you outlined, `RAILS_ENV=test` seems needed. Any comment about the `rake db:reset` error at all?
      singulars
      1. PO
      1. USPaul Fioravanti
    2. COAnswer updated with some more detail. The problem is that the rake task does use the "test" configuration in the database.yml, but that config has already been put into a global hash and the Rails.env variable was interpolated and the value for the 'database' key in the configs is now set to development for the lifespan of the app, which in this case is the rake task. SO when you set RAILS_ENV=test, it's setting the database setting to test.sqlite3 for any block in which you've used <%= Rails.env %>
      singulars
      1. PO
      1. USLukas Eklund
    3. COThank you once again for the update, and for its detail. A well deserved accept. I guess as long as I use my Travis CI-specific **config/database.yml** file, I'll just have to deal with the small inconveniences.
      singulars
      1. PO
      1. USPaul Fioravanti
 

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