{{ message }}
fix: only write AI model prices that changed - #27923
Merged
Merged
Conversation
Contributor
Author
ssncferreira
force-pushed
the
ssncf/ai-model-prices-skip-unchanged
branch
from
August 6, 2026 15:38
af32a32 to
94d27db
Compare
ssncferreira
force-pushed
the
ssncf/ai-model-prices-skip-unchanged
branch
from
August 10, 2026 14:56
94d27db to
9690f4b
Compare
ssncferreira
marked this pull request as ready for review
August 10, 2026 15:03
johnstcn
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, the AI Gateway price seeder rewrote every row of
ai_model_priceson each server start, becauseON CONFLICTfires on a key conflict rather than on a value difference.updated_attherefore recorded when the server last restarted rather than when a price last changed.Guard the
DO UPDATEbranch so a conflicting row is only rewritten when one of its four prices differs. The comparison usesIS DISTINCT FROMrather than<>because the price columns are nullable, and<>yields NULL when either side is NULL, which would skip the update and leave a stale price in place.Related to https://linear.app/codercom/issue/AIGOV-567/experimental-cli-command-to-set-prices-for-unpriced-ai-models
Note
Initially generated by Claude Opus 5, modified and reviewed by @ssncferreira