You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Invalid entry: 51 Should be:50
Invalid entry: 52 Should be:51
Invalid entry: 53 Should be:52
Invalid entry: 54 Should be:53
Invalid entry: 55 Should be:54
Invalid entry: 56 Should be:55
50th entry is skipped by the cursor during iteration.
In this case ups_cursor_move(cur, &key, &rec, 0) was inserted to simulate situation when there is a possibility for invalidation of key/rec values by subsequent ups api calls, so just before reading them I want to update their values according to cursor position. (I actually experience this scenario in my app).
Since ups_cursor_find(cur, &key, &rec, UPS_FIND_GEQ_MATCH) is also required is this issue connected to #105 ?
The text was updated successfully, but these errors were encountered:
If the unittest created for issue cruppstahl#46 (Approx/issue46Test) was written
correctly then one of the problems related to issue cruppstahl#106 would be caught
much earlier.
Please consider following sample:
What is printed to the output:
50th entry is skipped by the cursor during iteration.
In this case
ups_cursor_move(cur, &key, &rec, 0)
was inserted to simulate situation when there is a possibility for invalidation of key/rec values by subsequent ups api calls, so just before reading them I want to update their values according to cursor position. (I actually experience this scenario in my app).Since
ups_cursor_find(cur, &key, &rec, UPS_FIND_GEQ_MATCH)
is also required is this issue connected to #105 ?The text was updated successfully, but these errors were encountered: