# Gotchas

## ActiveRecord

* `find` raises an exception that if not handled, will result in controller endpoints returning 404.
* `find_by!` is a variant that can be used to get the same behavior of `find` for `find_by`.

## database.yml

If you try to have a generic database configuration controlled by environment variables, your database actions will run twice in development.

e.g.

```yaml
default: &default
  adapter: postgresql
  encoding: unicode
  pool: <%= ENV['DATABASE_POOL'] %>
  host: <%= ENV['DATABASE_HOST'] %>
  database: <%= ENV['DATABASE_NAME'] %>
  username: <%= ENV['DATABASE_USER'] %>
  password: <%= ENV['DATABASE_PASSWORD'] %>

development:
  <<: *default

test:
  <<: *default
```

Since Rails by default runs migrations for the `test` environment when you're on `development` , when it tries to run them the `RAILS_ENV` will be `development` so it will actually run all the database actions on the development database again.

Instead ensure that you give specific and unique names for the development and test environments:

```yaml
development:
  <<: *default
  database: my_app_development

test:
  <<: *default
  database: my_app_test
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.omar.engineer/programming-languages/ruby/ruby-on-rails/gotchas.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.