1. #1
    Sencha User
    Join Date
    Mar 2012
    Posts
    39
    Vote Rating
    0
    nbester is on a distinguished road

      0  

    Default Unanswered: ST2.1 - Store Load() then Sync() deletes records

    Unanswered: ST2.1 - Store Load() then Sync() deletes records


    I am upgrading my app to ST2.1 from 2.0.1.1 and I am having trouble with strange behaviour when loading a server store. I have run the same app against the two SDK versions to highlight the difference.

    Information on the store.
    1. It has a server Rest proxy
    2. In the experiment it has 9 records which gets loaded when reader is called
    3. Two local records are added at startup.

    Behaviour with ST 2.0.1.1:
    After first load data on the store is as follows:
    couchCourseStore has 11 records: 0 new; 0 removed; 9 updated;

    After the second and subsequent loads the store info as follows:
    couchCourseStore has 11 records: 0 new; 0 removed; 9 updated;

    Behaviour with ST 2.1b3:
    After first load data on the store is as follows (same as with ST2.0.1.1):
    couchCourseStore has 11 records: 0 new; 0 removed; 9 updated;
    After the second load, however, the information changes to the following
    couchCourseStore has 11 records: 0 new; 11 removed; 9 updated;

    Here it now shows 11 removed records. When I now want to sync this store, it deletes all my records! I have combed the forum and found an issue here which sounds very similar. Could it be that this problem is re-surfacing in the new version?

  2. #2
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    37,548
    Vote Rating
    873
    Answers
    3566
    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


    You may want to follow that bug report then.
    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 User
    Join Date
    Mar 2012
    Posts
    39
    Vote Rating
    0
    nbester is on a distinguished road

      0  

    Default Will track with original problem

    Will track with original problem


    OK, will do so. There just has been no activity on that tread for about 4 months, so I assumed (hoped really) that it has been fixed and just got lost. Checking it now I see it was never closed:fixed.

  4. #4
    Ext JS Premium Member
    Join Date
    Jul 2008
    Location
    Ottawa, Ontario
    Posts
    3
    Vote Rating
    0
    aberlinguette is on a distinguished road

      0  

    Default


    Just wondering what the status of this bug is or if anyone has any valid workarounds?

    Thanks,
    Marc.

  5. #5
    Sencha User
    Join Date
    Mar 2012
    Posts
    39
    Vote Rating
    0
    nbester is on a distinguished road

      0  

    Default My workaround

    My workaround


    Mark,

    I made a comment here on a workaround that works for me. It could be highly specific to what I am doing but it takes my problems away for now..

    I overloaded the "doDataRefresh" function on store as indicated...

    I have no info on the longer term fix..