What do you expect to get back in this case? Using a buffered store only some portion of the data set is going to be available locally. In old versions this ended up calling code that would produce a result, but that result is a bit suspect. So when we changed to page caching we did not try to replicate the interface where we could see no meaningful way to achieve the goal of the API.
Just curious if this is a case we missed or not. Thanks!
Yes Don, we load grid with many records based on different request and rendering a grid using different renredrer on columns takes up a lot of time. With buffered grid, the load/render time is always the same, great experience for the user (thanks for that!).
We have a bug with the buffered grid however and I can't tackled down the root of the problem. So I decided to give 4.2 a shot, you know to change my mind and to see how things work with 4.2. The problem I have in my app described in this thread is not happening in 4.2
Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..."