Skip to content
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

Explicitly declare insert columns #53

Merged
merged 1 commit into from
Nov 1, 2024

Conversation

mellypop
Copy link
Member

@mellypop mellypop commented Nov 1, 2024

To create raptr.bam_tpl_read_group I renamed raptr.bam_tpl_loadable, added the read_group_id column, backfilled it, and dropped the loadable_id column. Previously, bam_tpl_id and loadable_id were the first two columns, so when add_bam_pair_xenocp.py tried to insert using insert into raptr.bam_tpl_loadable values (%s, %s) without explicitly stating the columns being inserted, everything was fine, but now that the columns have moved around, postgres thinks it's trying to insert values for bam_tpl_id and inserted_time because those are the first two columns.

This PR updates the insert statement to explicitly declare the columns being inserted.

@mcrusch mcrusch merged commit 97476af into main Nov 1, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants