Unverified50% confidenceEventExact time
On September 29, two database migration scripts with the same number had both already been executed in production, so they could only be moved away and redone; afterward, a rule was added: scan all parallel branches and worktrees before taking a number.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedBackward-compatible database migrations follow the expand-contract pattern: first add the new column while retaining the old one, then delete the old column after the application code has fully switched over, with the two phases spanning separate deployment cycles.66% similarUnverifiedOn October 10 and 11, the script received a 521 directly when requesting the collection list; because that call had no retry mechanism, the entire phase failed without writing data, whereas URL queries had already had retries added since August.62% similarUnverifiedWhen updating a document, a delete-then-insert strategy at the document level is more reliable than chunk-by-chunk comparison updates, because under fixed-length chunking, modifying the beginning of a document causes all subsequent chunk boundaries to shift.56% similarUnverifiedError-fix solutions for outdated and mutually conflicting data include: storing source, version and last-updated-date metadata for each text chunk; re-indexing when documents change or rebuilding the index on a fixed cycle; removing or filtering superseded versions; and showing the source and its date in the answer.55% similarUnverifiedOn September 16, an enterprise payment approval system had version tags applied twice on the same day, and neither version had a changelog or a handover note.54% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1045968API
curl https://kongchang.com/api/v1/knowledge/claims/1045968MCP
get_claim(id=1045968)