activerecord

That means I don't need to update it when ActiveRecord or Sequel or Mongoid gets a new feature.

Enjoyed the article, it describes most of the issues I had with ActiveRecord.

Ernie Miller manages to dissect a few gnarly parts of ActiveRecord while keeping it positive and constructive.

In ActiveRecord you would have to specify for each model to which the database to connect.

He reinvented ActiveRecord associations, incorrectly because he didn't like that the column name had to have `_id` at the end.

Is there any guidance out there about when to use activerecord-jdbc-adapter vs this gem (for postgres)?

Part of this is because you can't rely on stuff like ActiveRecord, ActionController, etc.

But there is no doubt a big lag with activerecord.

As someone who is just dipping my toes into Rails (but has used plenty of other ORMs in other languages): ActiveRecord doesn't have native left join support?!

I've been wishing for a while though that Rails ActiveRecord would support the atomic partial update operations inside hstore that postgres already does.

Maybe you've worked with ORMs like ActiveRecord and/or Sequel.

Isn't what you're describing essentially the ActiveRecord pattern?

The workaround some people will suggest is "replace ActiveRecord with Sequel" but for existing projects a migration to a less standard Rails stack may not be viable.

I realize it's not part of the standard Rails stack, but it actually makes upgrading Rails easier because you're not constantly chasing a non-standard API that changes release to release (even on MRI, ActiveRecord "plugins" break with almost every release).

"But there is no easy way to do this in ActiveRecord without sacrificing eager loading." Define a relationship: has_many:approved_comments, class_name: "Comments", condtions: {approved: true} Then eager load approved_comments.