All migrations are wrapped in transaction by default so that they can be rolled back when they are failed. You need to use disable_ddl_transaction when you want to do something that can not excute inside a transaction. You can check Transactional Migrations section of Migration document for example.
This is a fairly recent addition to Rails, so it may not be covered in the book you mention. You can read about it in the migration section of Rails Guides. When you generate using, say, rails generate model Thing name post:references … the migration will create the foreign key field for you, as well … Read more
As of Rails 5.0 you can use the _prefix or _suffix options when you need to define multiple enums with same values. If the passed value is true, the methods are prefixed/suffixed with the name of the enum. class Invoice < ActiveRecord::Base enum verification: [:done, :fail], _prefix: true end It is also possible to supply … Read more
Well, another problem with your random filename generator is that it’s possible to have collisions isn’t it? You could possibly generate a filename that was already generated. One way to go about it would be to somehow generate a hash based on unique properties of the image, like file path. An example, from the carrierwave … Read more
This should work in Rails 3.2 and Rails 4: post.association(:tags).add_to_target(Tag.first) See this gist: https://gist.github.com/betesh/dd97a331f67736d8b83a Note that saving the parent saves the child and that child.parent_id is NOT set until you save it. EDIT 12/6/2015: For a polymorphic record: post.association(:tags).send(:build_through_record, Tag.first) # Tested in Rails 4.2.5
I don’t think that default Rails validators will do the trick here, you can do this though: validate :validate_wdays def validate_wdays if !wdays.is_a?(Array) || wdays.any?{|d| !(0..6).include?(d)} errors.add(:wdays, :invalid) end end
It’s to allow subclasses to reuse the create implementation provided by devise, but being able to hook into the process. For example you might have something like class MyRegistrations < Devise::RegistrationsController def create super { |resource| … } end end
I guess it depends on what you want: Rails style code generation (where it generates code for you that you can modify) Django style semi magic where admin forms can be derived from the fields in your table/document schema. you mean generating an API for these fields in the database, ala what grape does for … Read more
Yes, it has changed in Rails 4. Take a look at the Http::Headers code. Now custom variables are always prepended with HTTP_ and _ in your variables are replaced with -, except for CGI variables. HTH EDIT: Just checked again, – in variables are getting replaced with _ and being prepended with HTTP_. In above … Read more
TL;DR The most direct way to check this is to sort the arrays before checking their equality. json.map{|d| d[“id”]}.sort.must_equal Database.all.pluck(:id).sort Still here? Okay. Let’s talk about comparing elements in an array. As it is, the map{} is already somewhat irrelevant to the test and adding clutter, I’d prefer to not add even more. Well, that … Read more