Re: [Rails] Re: rails vs. nodejs

I started two project scheduled for next three months last week. I chose Rails. The project is technically complete. With some UI overhauling we can present to client. That's the power of Rails. On Wed, Nov 14, 2018 at 12:24 PM Jack Waugh wrote: > It's late 2018. Is Ruby still what managers are

Re: [Rails] Consistency between database constraints and ActiveRecord validations (database_consistency gem)

Hi, thank you! I'm wondering whether our tools different in how they treat different cases. > Oh, I wish I find it earlier :) I could check your implementation. My way is described in the README. What other features are planning on implementing? > I don't know yet. But I see you have few

Re: [Rails] Consistency between database constraints and ActiveRecord validations (database_consistency gem)

Nice work! I implemented a similar feature in active_record_doctor and I'm wondering whether our tools different in how they treat different cases. What other features are planning on implementing? Best regards Greg Navis -- You received this

[Rails] Database based uniqueness validations for ActiveRecord

You may have noticed that Rails is performing a *SELECT 1 FROM *query before inserting a new record if there's a uniqueness validation in the model. This approach has several downsides. First of all, it's an additional query, and in case there's uniqueness validation on several attributes,

[Rails] Consistency between database constraints and ActiveRecord validations (database_consistency gem)

After a while of development your project, you might notice that you have some inconsistencies between your database constraints and validations. Right now, we will talk about two possible situations. *Case #1.* Imagine you defined your table as following: create_table :users do |t|