# Exact explanation of embedded models

**URL:** <https://discuss.emberjs.com/t/exact-explanation-of-embedded-models/2022>\
**Category:** Ember Data\
**Created:** [August 2, 2013, 9:05pm UTC](https://discuss.emberjs.com/t/exact-explanation-of-embedded-models/2022 "2013-08-02T21:05:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![GlobeCoder](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/globecoder/32/14356_2.png) [@GlobeCoder](https://discuss.emberjs.com/u/GlobeCoder)\
**Post date:** [August 2, 2013, 9:05pm UTC](https://discuss.emberjs.com/t/exact-explanation-of-embedded-models/2022/1 "2013-08-02T21:05:09Z")

</div>

I have been working quite a bit now with emberData and apart there are still a few things I don’t quite understand, one of the latest being what exact implications it has if I sideload a `hasMany` relationship, or if I set it to `embedded: load` or `embedded: always` The problem I ran into was, we have a `User` model that has many `Events`. If we set the `Events` model as `embedded: load` and fully include it in the `User` model that works, but then `App.Event.find(id)` doesn’t work all of the sudden anymore, what we need for a permalink to the event. We now changed it to simply sideload the `Event` model, but it would still be interesting to hear about the exact differences, as well as pros/cons for these 3 different techniques. Thanks