MSSQL Stored Procedure to generate an Ext JS Model

I've been using a stored procedure written by Leon C. Tayson to generate c# objects based on tables in SQL Server and decided to change it to generate an Ext JS model to save typing. Here is the version I've modified spit out an Ext.data.Model:

Sencha Architect version?

Will there a version that could be used to create models within Sencha Architect. I have a table with >100 fields and would like to auto-generate the model. Currently I would comma-delineate it but it will not have the nice types and 'MS' date field config that the Stored Procedure creates for me. Any ideas?

Twitter - @evantrimboli
Former Sencha framework engineer, available for consulting.
As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.

I created a small lookup version of the model with only five fields linked to a different store that only loads and the displays the data the grid needs. I am still creating the model with the 100 fields. One field at a time. I was able to paste in comma delineated fields, but now I have to enter each field's data type. Sencha Arch, needs a model builder! from SQL, Delineated file, xml or something. Working in the UI for each field is time consuming. Nothing some patients and cool music can't fix. thanks for the reply it validated some decisions I have made this afternoon!

Most of my models reside in an /appname/include/models.js which I manually paste in from the stored procedure and modify accordingly. I generally avoid creating models in SA because I'm often changing the URLs to proxies (with different subfolders, etc) in my stores and then assigning the store back to a grid. I could probably improve the way I'm doing this, but when I started using Ext JS, I wasn't too sure about the new REST proxy; it may have matured/stabilised by now.

Loving your work!

Marc,
really appreciated what you've done! It saves no end of time. I have Ext Designer but found it extremely slow so I tend to hand code a lot of my projects. I've expanded on what you've provided to add the store.

The my app structure is as follows:
\MYAPP\app\view
\view\ui
\store
\php\ <-- all get and set methods go in here

I use a lot of views in SQL and I always convert datetime to varchar: CONVERT(varchar, myDate, 120) as dtMyDate

I have therefore added a filter to look for 'dt' at the start of the field name and set that as a date type.

I'm thinking of using stores and models more appropriately in my next project, so I may just use what you've further elaborated. I have been sending my own AJAX requests with appropriate GET/PUT/POST/DELETE methods but I think I will actually use the REST store/model/proxy whatever it is next time, and a stored proc to do more is just what the doctor ordered. Thanks.