>Hello Cetin,
>
>"With buffering = 3 the user already shooting himself on the foot on his/her will IMHO."
>
>I can't agree with that, I made this settings intentionally cause i'm 100% sure that there is never more than 1 record in these cursoradapters (only used for updating one record by id) and that there is also no record pointer movement.
>
>And I think it is a bug, a REQUERY() command on a normal view in a DBC which is the equivalent function
>for CursorFill/Refresh on a CursorAdapter also does not behave this way if I remember correctly.
>
>At the very least it should be mentioned in a thick red "beware" box in the documentation.
>
>Christian

Christian,

Regardless of how many records will be dirty row buffering does automatic magic stuff whenever the record pointer moves and table buffering does not. To me that means if you don't want to get hit with automatic magic stuff then DO NOT USE ROW BUFFERING EVER FOR ANY REASON AT ALL becasue it does magic stuff.