> For the complete documentation index, see [llms.txt](https://clear.gitbook.io/project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clear.gitbook.io/project/model/associations/has_one.md).

# has\_one

Has many represents the second counter part of [belongs to](https://clear.gitbook.io/project/model/associations/belongs_to) relation. It assumes the current model is referenced by an object (or no objects) of another model.

Usually, it's used when another model optionally extend the current model by composition. A common example is the usage of `User` and `UserInfo`. `UserInfo` is setup after registration and filling of form from the user. An User can then exists without `UserInfo` – this handle all the connection lifecycle – while `UserInfo` will handle all the optional informations about the user.

```ruby
class User
  include Clear::Model

  primary_key

  has_one user_info : UserInfo
end

class UserInfo
  include Clear::Model

  primary_key

  belongs_to user : User
end
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://clear.gitbook.io/project/model/associations/has_one.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.