# Cheap many to many

There are two common ways to establish a many-to-many relationship:

1. `has_and_belongs_to_many`
2. `has_many, :through`

Both require a join table, and the second requires a little more setup than the first bit is more future-proof.

A third alternative is so simple it sounds dumb: simply add a JSON column to the parent that contains an array of child IDs. If you understand the constraints of this approach and your use case doesn't need them, it can be a flexible and noncommittal way to model relationships.

## Downsides

* No guarantee of data integrity (can have orphaned IDs, no `dependent: destroy`, etc.).
* Cannot access list of parents from child (can't see who a model belongs to).
* Worse performance (or, at least, unmanaged performance).

## Advantages

* Very noncommittal. When working with uncertainty, it's good to be as flexible as possible until you are sure of requirements. Creating a table is *very* committal.
* Automatic transactions. Simply update the parent record without needing to worry about data inconsistency.
* Can easily migrate to a true join-table based relationship.


---

# 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://timhwang21.gitbook.io/index/programming/rails/cheap-many-to-many.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.