Matt Broadstone

@omayhemo maybe this tip would help you: https://github.com/dchester/epilogue/issues/167#issuecomment-223343235 ?

oh right I see what you're saying. no, presently we don't have any way of setting some sort of option to execute a `sequelize.query("raw data in here")`. You have two...

no, in fact I don't believe `context.query` is a thing. according to do the [docs](http://docs.sequelizejs.com/en/latest/api/model/#build), the raw option does the following: ``` [options.raw=false] Boolean If set to true, values will...

@semaja2 have you tried using auto association? Otherwise it might be useful to put together a simple test case that we can develop against.

@jblaketc you can do a `write.before` for the list controller and inject `{ count: 1000 }` to the `req.params`

there is internal tracking done by sequelize, which we use here to determine if a reload is required: https://github.com/dchester/epilogue/blob/master/lib/Controllers/update.js#L53

@TheMallen yeah I've been exploring different options. In terms of just providing all of the auto-generated routes for deep associations, it's not that difficult. What _is_ difficult with the current...

Yeah, you've definitely hit the root of the problem: we need a way to have sub resources. I'm currently slogging through generating all the proper endpoints for @sharathm 's usecase...

@kckolz @philotas is correct, if you assign a milestone method where one already exists it's added to the stack so your code here would be run after the default method.

@kckolz you actually might be exposing a bug wrt [this](https://github.com/dchester/epilogue/blob/master/lib/Controllers/create.js#L18) line. We automatically `extend` `context.attributes` with `req.body`, which would cause problems if you wanted to directly modify it. A PR...