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
Currently it is not possible to update the primary key/xata_id on next branch, however it is possible via SQL. We should change our API to allow this.
Potential ways to fix:
We could send a new flag/param to control whether the primary key value should removed from update payload if supplied.
We could simply stop removing the value when the call is sent with the first param as the primary key and the second param as an object that contains a new value for this field
?
To Reproduce
Expected behavior
Software version
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
Related: https://github.com/xataio/frontend-next/issues/3761
Currently it is not possible to update the primary key/xata_id on next branch, however it is possible via SQL. We should change our API to allow this.
Potential ways to fix:
To Reproduce
Expected behavior
Software version
Additional context
The text was updated successfully, but these errors were encountered: