syzer

Probably not

is this technology enterprise ready? :)

+1

We have Person, PersonTasks, Task, tables. (many to many) `site.related('model').add(modelInstance).then(doSomething)` add this extra model but you cannot save them. if you call `create`(instead add) then you get to store relation...

ok just for future references we did some stuff like this: ``` js Model.forge(toSave).save(null, {method: doc ? 'update' : 'insert'})) ``` so we tell bookshelf is the extra row in...

Further reading: http://blog.codinghorror.com/object-relational-mapping-is-the-vietnam-of-computer-science/ Basically set theory (aka the database) and object orientation do not go together.

Look on test: ``` it('eager loads hasMany `through`', function() { return Blog.where({site_id: 1}).fetchAll({ withRelated: 'comments' }).then(checkTest(this)); }); ``` attach/detach work ok with one-to-many but many-to-many (via proxy table) currently requires...

well i can't explain that better.. one-to-many: you will get to work under 2 hours many-to-many in 8 hours...

and then you will hate orm's like most ppl ;)

:D