On Wed, May 25, 2011 at 4:15 PM, pramod.deore <[email protected]> wrote: > > On May 25, 12:08 pm, Nikolay Elenkov <[email protected]> > wrote: >> On Wed, May 25, 2011 at 4:01 PM, pramod.deore <[email protected]> >> wrote: >> > Hi Ravi thanks for reply. actually it will becomes more complicated. >> > Because server is sending data 2-3 times within a second And it will >> > not be good idea to store data such a frequently. >> >> > Can somebody please provide me a guideline How I can check whether >> > some key (here Name ) is already exist in listview? >> >> If you don't have much data to deal with it, it might be easier to >> just replace everything and re-display. It doesn't really matter >> what exactly changed. > > Actually I am dealing with huge data. In above code just show a sample > of three fields but there are more than 40 fields.
Why is top-posting the norm on this list? Please write your reply *below* the previous one, so it reads like a conversation. Trimming also helps. How are you going to display 40 fields in a ListView? It doesn't really matter though, you usually care if a particular row/record changed and update/replace the whole record in your model/adapter. If you want to be able replace a particular record, use some key (e.g., the employee ID) to search for it, and update/replace it. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
