11 Nov 2011 2:44 AM #11
any new on that Issue? if this going to be included in the ExtJS's official release?
24 Jan 2012 7:14 AM #12
Count me in,
I'm looking forward for this feature to be included in ExtJS
1 Feb 2012 11:25 PM #13
and I would call this a bug, because why do we have a model class system with associations, if we aren't able to save a complete object graph? And the scenario to always make a step-by-step saving (first save the store of the association, then save the root object) isn't the best saving method, isn't it?
If you have complex object graphs you have to ensure you are sending the complete graph to the server, so it saves this object transactionally to the the database - if we don't do this we have to skip our ORM and have to deal with foreign key problems and so on...
so... sencha? any comments?
13 Feb 2012 4:58 PM #14
Same issue here
@Sencha, Is this fixed in extjs 4.1?
2 Mar 2012 9:09 AM #15
BUMP. Any news on this?
6 Mar 2012 12:28 PM #16
12 Mar 2012 12:25 PM #17
16 Mar 2012 4:10 AM #18
Really, this should be possible from within the framework. Otherwise, there's really no use using associations; it's probably less painful then to add another store and link everything manually. Is this planned for any near future releases?
16 Mar 2012 5:30 AM #19
Has anyone tried the 4.1 RC - as the issue seems fixed there:
Search for EXTJSIV-4464 - prepareAssociatedData method doesn't handle nested asssociations [Parature Inc]
22 Mar 2012 8:10 AM #20
At first take, this problem still appears to be happening for me w/ 4.1 RC1. I'm just using a model w/ a proxy (and not a store), but I don't think that should matter.