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

Populate and enforce last_status_number column of backend #758

Conversation

paulgb
Copy link
Member

@paulgb paulgb commented Jun 25, 2024

This bails from updating the backend status if the existing status is greater or equal to the new status.

If the existing last_status_number is NULL, this will always succeed.

Copy link

vercel bot commented Jun 25, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
plane ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 25, 2024 6:47pm

Copy link
Member

@rolyatmax rolyatmax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good - sorry for the nits, but it looks like the terms last_status, current_status, and new_status are being used in slightly confusing ways. Mind if we stick to the two terms last_status and new_status (or next_status) while in that function?

@paulgb paulgb merged commit 0d87b75 into main Jun 25, 2024
6 checks passed
@paulgb paulgb deleted the paul/dis-2212-populate-last_status_number-when-writing-a-backend-status branch June 25, 2024 19:23
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.

2 participants