-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
Batch updating column using /tables/
api should reference column using id
instead of column_index
#1167
Comments
@silentninja Can I work on this? |
@ratika-12 This issue needs some understanding of the codebase and Django. I will confirm in a few minutes, sorry for the wait. |
@ratika-12 I have assigned the issue to you, thanks! |
@ratika-12 I have updated the proposed solution to make it easier to understand. Let me know if anything is not clear. |
@ratika-12 Are you still working on this task? I figured I would follow up since it's been a while and there has not been a PR yet. |
@kgodey Yes I am working on this task. I will make a pr for this asap. |
@ratika-12 Are you still working on this task? Just wanted to follow up. Also please push your work to a draft PR, so that it is easy to follow up and suggest changes |
@kgodey @silentninja Can I work on this if this is not being worked on currently by @ratika-12? |
Yeah sure !! |
Thanks @Anish9901, assigned to you. And thanks for the update @ratika-12. |
@silentninja Does the attnums have to be passed as a list of attnums to a db layer function or does the |
This should be the preferred option |
Problem
Batch updating Columns using the
columns
field in thepatch
method of the/tables/{id}/
does not useid
of the column rather the column to update is identified based on the position of the column objects. This is not ideal due to the following reasons:column_index
which is deprecated in favour ofid
.Proposed solution
The following changes have to be made:
-
PATCH
method of the/tables/{id}
api which has the following structureshould be replaced with
attnums
which can be fetched from the column object before sending the column data from the service layer to the database layer(before calling any function from thedb
module)The text was updated successfully, but these errors were encountered: