New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Bug: PK not saving properly when adding row through UI #8351
Comments
Was able to reproduce on same system - seems like an onkeyup listener event is firing too quickly during entry of data into pk column which causes premature upsert into db. Short text entries in pk column typed at moderate pace (such that listener event doesn't fire before you're done entering data) seems to avoid this issue. i'm thinking nocodb's lack of being able to retroactively edit PK's coupled with the premature upsertion because of the listener event firing is causing data to be half uploaded depending on whatever the listener event saw at the time of firing. Tables without a pk (and hence columns that can be retroactively edited) seem to avoid the issue completely, can anyone else verify? Still new to nocodb so a little hesitant to trust my conclusion here.. |
fixed here should be available in OSS in next release |
thanks for the quick work though |
Please confirm if bug report does NOT exist already ?
Steps to reproduce ?
Desired Behavior
To save each row properly
Project Details
Node: v16.19.1
Arch: x64
Platform: linux
Docker: true
RootDB: pg
PackageVersion: 0.108.1
Attachments
No response
The text was updated successfully, but these errors were encountered: