🐛 Bug: PK not saving properly when adding row through UI about nocodb HOT 3 CLOSED

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..

from nocodb.

fixed here
https://github.com/nocodb/nocohub/commit/b6adcab79f1f33f5638be8e470bde4f3ef1aca92

should be available in OSS in next release

from nocodb.

fixed here https://github.com/nocodb/nocohub/commit/b6adcab79f1f33f5638be8e470bde4f3ef1aca92

should be available in OSS in next release

thanks for the quick work though
i think commit link is broken, any idea when next release might happen?

from nocodb.