title: Rails 5: Why dropping a specific table isnt as simple as typing a command like drop_table(users):?
body: <p>I wanted to get rid of some development experimentation so I started destroying my models and controllers and then I went to the db part of the job. Looking at previous answers like this <a href="https://stackoverflow.com/questions/4020131/rails-db-migration-how-to-drop-a-table">Rails DB Migration - How To Drop a Table?</a> and the API guide for Rails 5 I ve realized that dropping a specific table is not as straightforward as "rails destroy controller users"... But why is that?</p>
  
  <p>A previous stackoverflow post suggested running bundle exec... <em>before</em> going after the controller and models but I ve lost that ship now. </p>
  
  <p>In short: can someone describe with some technical insight the steps that I should go after to remove the remnant table <strong>in detail</strong> now AND explain to me why is not as simple to delete a specific table at this point?</p>
  
  <p>A best practice guide for rolling back experimentations would be appreciated.</p>