Open marty0678 opened 11 months ago
Hi @marty0678 thank you for letting me know. You can rollback to the old build here: https://tableplus.com/win/changelog
we will fix this bug and send yo hotpatch asap
Hi @marty0678, this issue is so weird. I could not reproduce it. Could you please take a record video of this issue? It' might help us to find out the problem. Thanks
@sonswift hey thanks for looking into it! I haven't been actually seen it since making this ticket and I've had no luck manually trying to reproduce it either. I'm still trying but I honestly have no idea what caused this or why but it hasn't had any issues today so far. If you want to close this ticket feel free as I realize without reproducible consistent steps I'm not much help haha.
Did you rollback to the old version of you are using the same version as the original report @marty0678 ?
Did you rollback to the old version of you are using the same version as the original report @marty0678 ?
Nah still on the latest / didn't revert so I could try to reproduce it.
Which driver are you using and version of it (Ex: PostgreSQL 10.0): MySQL 8.0.32
Which TablePlus build number are you using (the number on the welcome screen, Ex: build 81): 5.8.0 Build 256, Windows.
The steps to reproduce this issue: This seems random when it happens, but it's happening enough since updating to Build 256 over the last two days I wanted to report it. This did not happen previously.
Steps:
Expected: The new rows appear in the table I am currently on when I refresh. When I go to the other table, it is also updated with the new row data.
Actual: The new rows appear in the table I am currently on when I refresh. When I go to the other table, the order of the rows have changed, with some rows being gone completely, and some rows being duplicated. For example before the refresh an order of PKs might look like:
And after the refresh it may look like
If I do a hard re-connect (CTRL+SHIFT+R) it appears to fix it/go back to normal but I am still verifying this. It has happened to me about a dozen times over the last two days since updating to build 256, and it happens seemingly randomly, so I'm still trying to pinpoint exactly what is causing this as it's not easily reproducible.
As I discover / test more I'll update this ticket.