I can across that issue too. The way I am getting around most of these issues is just doing a row updates with If-Match and setting all of the columns to empty strings. The next insert that can use that row. This has worked so far for me.
I have also came across issues with concurrent row inserts (I did not have much time to investigate it but I think the API gives back the same row for two inserts). On Sat, Jul 12, 2014 at 11:41 PM, Adam Pritchard <[email protected]> wrote: > I have also come across this etag failure, and it combines horribly with > another row-delete bug. Reproduction: > > - Create a spreadsheet with title row and three rows underneath. > - Using the API, get the list feed for the spreadsheet. > - Using the API, delete the first row (i.e., the first list entry). > (Use If-Match or not — doesn’t matter yet.) > - Using the API, delete the second row (i.e., the second list entry). > Use If-Match. > - FAIL. The bottom (third) row disappears from the spreadsheet, rather > than the second. > > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Google Spreadsheets API" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-spreadsheets-api/8jUpojDdr3Y/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Google Spreadsheets API" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
