Home/ Questions/Q 7592995
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T21:03:13+00:00

I just realised that standard ActiveRecord actually hits the database when you do person

  • 0

I just realised that standard ActiveRecord actually hits the database when you do

person = Person.new(:name => "test")

I suspect ActiveRecord does this to check what fields are available for the model.

However, our legacy database is only occasionally available. That means that our test suite cannot run all the time. Are there any tricks to making this work without a database?

If it’s not possible, we thought of some alternatives:

  • have a local copy of the database and work on that one
  • use another ORM that solves this problem (DataMapper)

Any suggestions are welcome.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Working with a local copy is only possible if the data touched isn’t changed from anywhere else! Otherwise you will have a database disaster soon.

    Your suspection is right too. ActiveRecord checks the Database for fields so it needs a connection. I don’t think there is a way to solve this when you want continue using ActiveRecord. I think you need to solve the underlying problem and run a database that is always available!

    • 0