Create your own REPL by making a js file (ie: console.js) with the following lines/components: Require node’s built-in repl: var repl = require(“repl”); Load in all your key variables like db, any libraries you swear by, etc. Load the repl by using var replServer = repl.start({}); Attach the repl to your key variables with replServer.context.<your_variable_names_here> … Read more
Some things to try: Restart the rails console; changes to your models will only get picked up by a rails console that is already open if you do > reload! (although I have found this to be unpredictable), or by restarting the console. Is your model file called “phone_number.rb” and is it in “/app/models”? You … Read more
For an array, you can use one of these: # Will raise exception if any value not found User.find( [1,3,5] ) # Will not raise an exception User.find_all_by_id( [1,3,5] ) # Rails 3 User.where(id: [1,3,5]) # Rails 4 If you happen to be using a range, you can use these: # Will raise exception if … Read more
The accepted answer only works if you need to recreate the whole database. To drop a single table (with the callbacks) and to get the IDs to start from 1: Model.destroy_all # Only necessary if you want to trigger callbacks. ActiveRecord::Base.connection.execute(“TRUNCATE #{table_name} RESTART IDENTITY”) If you are using Sqlite, it does not support truncate so … Read more
I may be answering a bit late for this, but for the sake of the others who are looking for the answer… it’s here Basically, enter this command spring stop The issue , as far as I understand, is with the spring gem, specifically, it checks the server for versions, which doesn’t tally up. For … Read more
From How To – Persist Rails or IRB Console Command History After Exit. Create, or edit your ~/.irbrc file to include: require ‘irb/ext/save-history’ IRB.conf[:SAVE_HISTORY] = 200 IRB.conf[:HISTORY_FILE] = “#{ENV[‘HOME’]}/.irb-history”
As other have said, you want to use either puts or p. Why? Is that magic? Actually not. A rails console is, under the hood, an IRB, so all you can do in IRB you will be able to do in a rails console. Since for printing in an IRB we use puts, we use … Read more
reload! only reloads the latest code in the console environment. It does not re-initialize existing objects. This means if you have already instantiated any objects, their attributes would not be updated – including newly introduced validations. However, if you create a new object, its attributes (and also validations) will reflect the reloaded code. more here
Modern devise allows simpler syntax, no need to set the confirmation field user.password = new_password; user.save # or user.update(password: new_password)