Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It looks like that documentation is outdated.</p> <p>Try using devise generator, it will create same migration, with correct parameters, it's ok if its an existing model:</p> <pre><code>rails g devise customer </code></pre> <p>it should create <code>AddDeviseToCustomers</code> migration</p> <p>with something similar to this:</p> <pre><code>class AddDeviseToCustomers &lt; ActiveRecord::Migration def self.up change_table(:customers) do |t| ## Database authenticatable t.string :email, :null =&gt; false, :default =&gt; "" t.string :encrypted_password, :null =&gt; false, :default =&gt; "" ## Recoverable t.string :reset_password_token t.datetime :reset_password_sent_at ## Rememberable t.datetime :remember_created_at ## Trackable t.integer :sign_in_count, :default =&gt; 0 t.datetime :current_sign_in_at t.datetime :last_sign_in_at t.string :current_sign_in_ip t.string :last_sign_in_ip ## Confirmable t.string :confirmation_token t.datetime :confirmed_at t.datetime :confirmation_sent_at t.string :unconfirmed_email # Only if using reconfirmable ## Lockable # t.integer :failed_attempts, :default =&gt; 0 # Only if lock strategy is :failed_attempts # t.string :unlock_token # Only if unlock strategy is :email or :both # t.datetime :locked_at ## Token authenticatable # t.string :authentication_token # Uncomment below if timestamps were not included in your original model. # t.timestamps end def self.down # By default, we don't want to make any assumption about how to roll back a migration when your # model already existed. Please edit below which fields you would like to remove in this migration. raise ActiveRecord::IrreversibleMigration end end </code></pre> <p>note that there is no more <code>t.confirmable</code></p>
    singulars
    1. This table or related slice is empty.
    1. PODevise install from existing model/database
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAlper Karapınar
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODevise install from existing model/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. VTUpMod
    1. COWoudl it erase my current user?
      singulars
      1. PO
      1. USJseb
    2. CONo. Try it yourself in a dummy project :) Also, you can access [devise 2.0 document here](https://github.com/plataformatec/devise/wiki/How-To:-Upgrade-to-Devise-2.0-migration-schema-style)
      singulars
      1. PO
      1. USAlper Karapınar
    3. COThanks it works now i need to learn devise and use it properly
      singulars
      1. PO
      1. USJseb
 

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