> For the complete documentation index, see [llms.txt](https://docs.cycle-orm.dev/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cycle-orm.dev/en/general/readme.md).

# Introduction

### 📄 What is Cycle Active Record?

This library extends Cycle ORM by integrating the [Active Record pattern](https://en.wikipedia.org/wiki/Active_record_pattern), providing developers with an intuitive, object-centric way to interact with databases.

Unlike Cycle ORM's default Data Mapper pattern, which separates the in-memory object representations from database operations, Active Record combines data access and business logic in a single entity.

This allows for more straightforward and rapid development cycles, particularly for simpler CRUD operations, by enabling direct data manipulation through the object's properties and methods.

### ⭐️ Key Features

1. **Simplified Data Access**: Interact with database records through object properties and methods.
2. **Fluent Interface**: Chain methods for more readable and concise code.
3. **Built-in Query Builder**: Construct complex queries using an intuitive API.
4. **Automatic CRUD Operations**: Create, Read, Update, and Delete records with minimal code.
5. **Custom Query Classes**: Encapsulate and reuse complex queries.
6. **Integration with Existing Cycle ORM Features**: Leverage Cycle ORM's advanced capabilities when needed.


---

# 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:

```
GET https://docs.cycle-orm.dev/en/general/readme.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.