Hybrid View

  1. #1
    Ext JS Premium Member
    Join Date
    Feb 2011
    Posts
    28
    Vote Rating
    2
    shmeltex is on a distinguished road

      0  

    Default add method may not be called on a buffered store

    add method may not be called on a buffered store


    In ExtJS 4.1.3 ext-all-dev raises exception when trying to add a record to the buffered store. Is there a reason why adding records is bad practice? Should insert​ be used instead?

  2. #2
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    36,994
    Vote Rating
    846
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    AFAIK you are messing with the page maps of data when adding.
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  3. #3
    Sencha Premium Member
    Join Date
    Feb 2012
    Posts
    1
    Vote Rating
    0
    david.holland@tch.com is on a distinguished road

      0  

    Default Please elaborate

    Please elaborate


    Please invest more effort into maintaining backwards compatibility as you produce future releases; I have invested a lot of time into learning and using this framework, but I frequently get the impression you are treating it more like an application library for a couple of special clients than taking seriously the amount of pain you cause when you rip out major functionality like this.

    Having the ability to use "buffered" data stores to do batch type updates to my server is a huge win for me in ext-4.0.7; and now I also need to solve this problem... Time to diff the code and subclass Ext.data.Store, or could you recommend a better approach to using the data store interface to do
    time deferred batch updates.