Countdown to Ext JS 4: Anatomy of a Model http://www.sencha.com/blog/ext-js-4-anatomy-of-a-model If you follow Ext JS, chances are you already know that we have a brand new data package for Ext JS 4. The new data package builds on existing principles while adding a huge number of new capabilities. Follow along as Ed Spencer reveals more about this powerful feature of Ext JS 4. en-us ed@sencha.com Copyright 2011 2011-02-08T18:57:00+00:00 Comment by xml editor I agree with alex, the proxy issue is a real pain and it would be far easier to implement direct models. I agree with alex, the proxy issue is a real pain and it would be far easier to implement direct models.

]]> Tue, 13 Sep 2011 10:52 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:27024#date:10:52 Comment by Craig I do like removing the store from the picture, but then the question pops: for something like a grid panel or docked items (toolbar etc) - they all require a store, therefore exception is thrown and no data displays (granted I am brand new to extjs all together… been a JQuery guy for some time now, so this may be a silly question) so… how do we deal with that? I do like removing the store from the picture, but then the question pops: for something like a grid panel or docked items (toolbar etc) - they all require a store, therefore exception is thrown and no data displays (granted I am brand new to extjs all together… been a JQuery guy for some time now, so this may be a silly question) so… how do we deal with that?

]]> Tue, 16 Aug 2011 22:26 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:25397#date:22:26 Comment by Peter Regarding User data model, when I call User.load(‘123’,{..}), any idea I got the request like /users/123?_dc=12345788&id=123 rather than /users/123 ? How to remove parameter “id=123”? Thanks, Peter Regarding User data model, when I call User.load(‘123’,{..}), any idea I got the request like /users/123?_dc=12345788&id=123 rather than /users/123 ? How to remove parameter “id=123”?

Thanks,
Peter

]]> Tue, 26 Jul 2011 19:41 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:24554#date:19:41 Comment by Real Chan my data is xml file… my data is xml file…

]]> Mon, 25 Jul 2011 07:35 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:24487#date:07:35 Comment by Real Chan I’ve got the same concerns as ‘Christiaan’ above. “ In your example where you regModel User, you say hasMany: ‘Orders’ (plural). I dont see anything called Orders. I see a model called order (singular). What’s the meaning of a hasMany property referring to something that does not exist in the example? The Sencha Touch API docs shows this (which makes more sense) hasMany: {model: ‘Product’, name: ‘products’} “ I want to know how do you deal with them. I’ve got the same concerns as ‘Christiaan’ above.
“
In your example where you regModel User, you say hasMany: ‘Orders’ (plural). I dont see anything called Orders. I see a model called order (singular).
What’s the meaning of a hasMany property referring to something that does not exist in the example? The Sencha Touch API docs shows this (which makes more sense)
hasMany: {model: ‘Product’, name: ‘products’}
“
I want to know how do you deal with them.

]]> Mon, 25 Jul 2011 07:13 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:24482#date:07:13 Comment by Jay Can I use string as id? I noticed the documentation for model said it is strictly for number: load( Number id, Object config ) : void STATIC Can I use string as id? I noticed the documentation for model said it is strictly for number:
load( Number id, Object config ) : void STATIC

]]> Thu, 30 Jun 2011 08:22 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:23643#date:08:22 Comment by agenzie di modelle WOW ! This blog Looking soo great. Again,I love this post very much. I am aggre with you. This is your hopeful post.  I’ve got the same concerns as ‘cmwalolo’ above. Being able to call just the “users” (to show a list of user data only) vs having to load “users” + “orders” + “order items”.... well, that raises some major concerns on my part. Why shuffle data around from server to client that might not be needed? Regards,    Thans for shering. WOW ! This blog Looking soo great. Again,I love this post very much. I am aggre with you. This is your hopeful post.  I’ve got the same concerns as ‘cmwalolo’ above. Being able to call just the “users” (to show a list of user data only) vs having to load “users” + “orders” + “order items”.... well, that raises some major concerns on my part. Why shuffle data around from server to client that might not be needed?
Regards,    Thans for shering.

]]> Sat, 07 May 2011 11:51 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:20740#date:11:51 Comment by Andreas ... and it happened again, just 2 hours after my last comment. 20 new unread items in the sencha feed, all pretty familiar. *sigh* ... and it happened again, just 2 hours after my last comment. 20 new unread items in the sencha feed, all pretty familiar. *sigh*

]]> Sat, 19 Feb 2011 09:50 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17523#date:09:50 Comment by Andreas @David Kaneda: Thanks, it happened again just today, so there still seems to be a problem with the RSS feed. @David Kaneda: Thanks, it happened again just today, so there still seems to be a problem with the RSS feed.

]]> Fri, 18 Feb 2011 23:55 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17509#date:23:55 Comment by Patrick Fraley When I see this I get tears in my eyes, tears of joy.  My brain is already planing the marriage of these models with mongodb ... You guys never cease to amaze me, every version of ext you delivered I though, awesome, can’t get better then this ...  And then the next version appears on the horizon   Keep up the good work ... Looking forward to playing around with this ... When I see this I get tears in my eyes, tears of joy.  My brain is already planing the marriage of these models with mongodb ...

You guys never cease to amaze me, every version of ext you delivered I though, awesome, can’t get better then this ...  And then the next version appears on the horizon smile  Keep up the good work ...

Looking forward to playing around with this ...

]]> Fri, 18 Feb 2011 10:51 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17471#date:10:51 Comment by AP Looks like some great stuff. The only question I have is: will you also have a HasAndBelongsToMany relationship, where both Models can have associations to many of the other model? If this will not be there directly, will it be extensible enough for us to “add” it in? Looks like some great stuff. The only question I have is: will you also have a HasAndBelongsToMany relationship, where both Models can have associations to many of the other model? If this will not be there directly, will it be extensible enough for us to “add” it in?

]]> Wed, 16 Feb 2011 05:06 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17348#date:05:06 Comment by David Kaneda @Dmitry, @Mike, @Andreas — Very sorry for the troubles guys. We’ve had a few issues about the feeds pointed out since launch, and I get the feeling it reloads the feed each time we change the template. I don’t believe this will continue through new posts, but will keep a close eye on it. @Dmitry, @Mike, @Andreas — Very sorry for the troubles guys. We’ve had a few issues about the feeds pointed out since launch, and I get the feeling it reloads the feed each time we change the template. I don’t believe this will continue through new posts, but will keep a close eye on it.

]]> Thu, 10 Feb 2011 09:30 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17170#date:09:30 Comment by Alexey I think current models are too coupled with proxies. In my application I use persistence.js and implementing custom proxy for it is real pain. Also it is very bad that controls, such as DataView require to use ext store. In my case it would be much simplier to use my persistence.js models directly. I think current models are too coupled with proxies. In my application I use persistence.js and implementing custom proxy for it is real pain.

Also it is very bad that controls, such as DataView require to use ext store. In my case it would be much simplier to use my persistence.js models directly.

]]> Thu, 10 Feb 2011 06:58 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17160#date:06:58 Comment by Alexey Does belongTo association supported inside XTemplate? Could you provide some simple example. Does belongTo association supported inside XTemplate? Could you provide some simple example.

]]> Thu, 10 Feb 2011 06:52 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17159#date:06:52 Comment by Alexey Do HTML 5 LocalStorage supports Associations? Do HTML 5 LocalStorage supports Associations?

]]> Thu, 10 Feb 2011 06:48 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17158#date:06:48 Comment by ibnesayeed According to Microformat RESTful URL documentation given in the post, URLs should have an extension attached to them to convey the desired response format (no extension defaults to HTML). proxy: {   type: ‘rest’,   url : ‘/users’,   reader: ‘json’ } For example, above configuration should generate following URLs. GET /users.json GET /users/1.json POST /users/1.json[?_method=PUT/DELETE] Similarly, if reader is configured for XML, then URLs should contain “.xml” suffix instead of .json. Will ExtJS 4 support this convention automatically (or may be a configuration for this pattern?) I am concerned about this, mainly because I use Ruby on Rails with ExtJS. And I configure my Rails application to respond in HTML, JSON and XML all three formats. HTML for SEO purposes, JSON to serve my ExtJS application and XML for cross-site web services. According to Microformat RESTful URL documentation given in the post, URLs should have an extension attached to them to convey the desired response format (no extension defaults to HTML).

proxy: {
  type: ‘rest’,
  url : ‘/users’,
  reader: ‘json’
}

For example, above configuration should generate following URLs.

GET /users.json
GET /users/1.json
POST /users/1.json[?_method=PUT/DELETE]

Similarly, if reader is configured for XML, then URLs should contain “.xml” suffix instead of .json.

Will ExtJS 4 support this convention automatically (or may be a configuration for this pattern?)

I am concerned about this, mainly because I use Ruby on Rails with ExtJS. And I configure my Rails application to respond in HTML, JSON and XML all three formats. HTML for SEO purposes, JSON to serve my ExtJS application and XML for cross-site web services.

]]> Thu, 10 Feb 2011 06:47 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17157#date:06:47 Comment by Andreas Yeah, the regular flooding with all recent posts on Sencha blog is starting to get on my nerves, too. Yeah, the regular flooding with all recent posts on Sencha blog is starting to get on my nerves, too.

]]> Thu, 10 Feb 2011 06:44 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17156#date:06:44 Comment by Mike I second the RSS comment.  I don’t want to unsubscribe, but may need to if I keep getting the entire feed history on every new post (using google reader) I second the RSS comment.  I don’t want to unsubscribe, but may need to if I keep getting the entire feed history on every new post (using google reader)

]]> Wed, 09 Feb 2011 21:57 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17120#date:21:57 Comment by Dmitry Please fix your RSS, it floods my reader for a week already after each new post! And please, put a link on a news title. Please fix your RSS, it floods my reader for a week already after each new post! And please, put a link on a news title.

]]> Wed, 09 Feb 2011 20:34 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17117#date:20:34 Comment by Andrew Peacock Hi, Looking great. Again, I’ve got the same concerns as ‘cmwalolo’ above. Being able to call just the “users” (to show a list of user data only) vs having to load “users” + “orders” + “order items”.... well, that raises some major concerns on my part. Why shuffle data around from server to client that might not be needed? Regards, Andy Hi,
Looking great. Again, I’ve got the same concerns as ‘cmwalolo’ above. Being able to call just the “users” (to show a list of user data only) vs having to load “users” + “orders” + “order items”.... well, that raises some major concerns on my part. Why shuffle data around from server to client that might not be needed?
Regards,
Andy

]]> Wed, 09 Feb 2011 12:59 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17104#date:12:59 Comment by Nicolas BUI @Francesco, @cmwalolo In the example, it seem that is not “in demand” at all. Instead, you have to provided the associated data directly in the base request. “On demand” or “lazy load” can be done but difficult to implement and would required many callback to be chained. @Francesco, @cmwalolo In the example, it seem that is not “in demand” at all. Instead, you have to provided the associated data directly in the base request.

“On demand” or “lazy load” can be done but difficult to implement and would required many callback to be chained.

]]> Wed, 09 Feb 2011 09:04 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17101#date:09:04 Comment by Martijn What I do not see is ext.direct support in sencha touch how about extjs 4 and direct? I love the approach of ext.direct…. What I do not see is ext.direct support in sencha touch how about extjs 4 and direct?
I love the approach of ext.direct….

]]> Wed, 09 Feb 2011 08:50 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17100#date:08:50 Comment by Francesco I have the same doubt as comment #2 I have the same doubt as comment #2

]]> Wed, 09 Feb 2011 07:27 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17099#date:07:27 Comment by Nicolas BUI It sound cool, but i would like to see real world usage When will we able to have an preview or beta release ? Best regards and hang on ! It sound cool, but i would like to see real world usage smile When will we able to have an preview or beta release ?

Best regards and hang on !

]]> Wed, 09 Feb 2011 00:07 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17089#date:00:07 Comment by John Thompson Looks pretty cool - can’t wait to try it out! Looks pretty cool - can’t wait to try it out!

]]> Tue, 08 Feb 2011 23:24 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17087#date:23:24 Comment by daiei27 P.S.  Thanks for these great blog entries. P.S.  Thanks for these great blog entries.

]]> Mon, 31 Jan 2011 20:06 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17075#date:20:06 Comment by daiei27 No wishlist here.  Just wanna say I welcome the improvements and I know you’re working hard to add more all the time. Can’t wait to try version 4 whenever it comes out! No wishlist here.  Just wanna say I welcome the improvements and I know you’re working hard to add more all the time.

Can’t wait to try version 4 whenever it comes out!

]]> Mon, 31 Jan 2011 04:05 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17084#date:04:05 Comment by Dmitriy Pashkevich 1) From the example above it seems that the convert function for a field is called automatically because of the line ‘console.log(abe.get(‘height’)); //logs 193 (inches converted to centimeters)’. Is this true or there’s an error in this example? 2) I second Christiaan’s question about hasMany with plural word as value. Maybe this is resolved automatically because there’s backward reference belongsTo in the Order model? And not specifying belongsTo in your example would break things? 3) Are the validations defined for a model only invoked manually or I can configure so that the validation is automatically performed, say, on ‘save’ action (similarly to form submit)? 1) From the example above it seems that the convert function for a field is called automatically because of the line ‘console.log(abe.get(‘height’)); //logs 193 (inches converted to centimeters)’. Is this true or there’s an error in this example?

2) I second Christiaan’s question about hasMany with plural word as value. Maybe this is resolved automatically because there’s backward reference belongsTo in the Order model? And not specifying belongsTo in your example would break things?

3) Are the validations defined for a model only invoked manually or I can configure so that the validation is automatically performed, say, on ‘save’ action (similarly to form submit)?

]]> Thu, 27 Jan 2011 00:23 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17083#date:00:23 Comment by Alexander Hartmaier I hope it will be also able to deal with mightHave relationships (when the foreign key column is allowed to be null). I hope it will be also able to deal with mightHave relationships (when the foreign key column is allowed to be null).

]]> Wed, 26 Jan 2011 15:50 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17082#date:15:50 Comment by Christiaan In your example where you regModel User, you say hasMany: ‘Orders’ (plural). I dont see anything called Orders. I see a model called order (singular). What’s the meaning of a hasMany property referring to something that does not exist in the example? The Sencha Touch API docs shows this (which makes more sense) hasMany: {model: ‘Product’, name: ‘products’} In your example where you regModel User, you say hasMany: ‘Orders’ (plural). I dont see anything called Orders. I see a model called order (singular).

What’s the meaning of a hasMany property referring to something that does not exist in the example? The Sencha Touch API docs shows this (which makes more sense)
hasMany: {model: ‘Product’, name: ‘products’}

]]> Wed, 26 Jan 2011 12:28 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17081#date:12:28 Comment by Dimitris I second question (2) from Alex. One of the most complex validations I’ve ever had to work with and one of the trickiest to get right is field inter-dependent validation. Let me give you a few examples: 1) Either field A or B is mandatory. 2) Neither A or B is mandatory, but if C is filled, one of them needs to be filled too. etc. Of course, most of the times you end up writing a custom function for these validations, but I’d like to see a framework that handles these in an elegant and consistent manner. I second question (2) from Alex.
One of the most complex validations I’ve ever had to work with and one of the trickiest to get right is field inter-dependent validation. Let me give you a few examples:
1) Either field A or B is mandatory.
2) Neither A or B is mandatory, but if C is filled, one of them needs to be filled too.
etc.
Of course, most of the times you end up writing a custom function for these validations, but I’d like to see a framework that handles these in an elegant and consistent manner.

]]> Wed, 26 Jan 2011 11:42 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17080#date:11:42 Comment by John Dunlap Looks awesome! You guys are definitely headed in the right direction here. However, I do have some comments that I would hope you would take as constructive criticism and not an effort to belittle your efforts because I can assure you that is not my intention!!! Having said that, I’m wondering the same thing as cmwalolo. Your new data package reminds me a lot of the JPA(Java Persistence API) which is a good thing in my book. However, JPA allows you to declaratively set the fetch type that you want to use to query an association. You set FetchType.LAZY on an association so that relationships between entities are not queried unless the data is actually needed or FetchType.EAGER on the association to immediately query all associated entities. It’s actually pretty important from a performance standpoint. You can bring the server to its knees pretty easily if you have a lot of entities with FetchType.EAGER associations to other entities because you end up unwittingly pulling large chunks of the database into memory with a single method call. The examples above remind me of FetchType.EAGER and I am worried that this could result in pulling a lot of data across the wire that your application may or may not have needed. Again, I appreciate your work, your work looks awesome, and I think you’re headed in the right direction! Cheers! -John Looks awesome! You guys are definitely headed in the right direction here. However, I do have some comments that I would hope you would take as constructive criticism and not an effort to belittle your efforts because I can assure you that is not my intention!!!

Having said that, I’m wondering the same thing as cmwalolo.

Your new data package reminds me a lot of the JPA(Java Persistence API) which is a good thing in my book. However, JPA allows you to declaratively set the fetch type that you want to use to query an association. You set FetchType.LAZY on an association so that relationships between entities are not queried unless the data is actually needed or FetchType.EAGER on the association to immediately query all associated entities. It’s actually pretty important from a performance standpoint. You can bring the server to its knees pretty easily if you have a lot of entities with FetchType.EAGER associations to other entities because you end up unwittingly pulling large chunks of the database into memory with a single method call. The examples above remind me of FetchType.EAGER and I am worried that this could result in pulling a lot of data across the wire that your application may or may not have needed.

Again, I appreciate your work, your work looks awesome, and I think you’re headed in the right direction!

Cheers!
-John

]]> Wed, 26 Jan 2011 11:33 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17079#date:11:33 Comment by Alex 1. Is there a reason why validations are a separate property of the model, rather than part of the field definition itself (like the conversion functions)?  If the validation is tied to a single field, it just feels like it would be more natural as part of that field’s definition. 2. Can you do multi-field validations?  i.e. the valid value of field B depends on the value of field A. 1. Is there a reason why validations are a separate property of the model, rather than part of the field definition itself (like the conversion functions)?  If the validation is tied to a single field, it just feels like it would be more natural as part of that field’s definition.

2. Can you do multi-field validations?  i.e. the valid value of field B depends on the value of field A.

]]> Wed, 26 Jan 2011 11:16 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17078#date:11:16 Comment by cmwalolo Does the data model get the children (only on demand) using the REST functionality as in this example ? GET /user/123/order/1 GET /user/123/order/1/orderitems or GET /order/1/orderitems Does the data model get the children (only on demand) using the REST functionality as in this example ?

GET /user/123/order/1

GET /user/123/order/1/orderitems or

GET /order/1/orderitems

]]> Wed, 26 Jan 2011 10:58 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17077#date:10:58 Comment by Jay Garcia Have you guys done performance tests w/ the new association modeling? Have you guys done performance tests w/ the new association modeling?

]]> Wed, 26 Jan 2011 10:41 GMT http://www.sencha.com/blog//ext-js-4-anatomy-of-a-model#id:17076#date:10:41