[#5] Uniformiser les timestamps SQLite pour éviter incohérences de tri et parsing #5
Labels
No labels
confidence:High
confidence:Low
confidence:Medium
effort:L
effort:M
effort:S
horizon:later
horizon:next
horizon:now
impact:High
impact:Low
impact:Medium
kind:feature
kind:improvement
priority:P0
priority:P1
priority:P2
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AI/orchai#5
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Le code mélange RFC3339 applicatif et datetime('now') SQL. Cette hétérogénéité fragilise les tris textuels et la cohérence des parsers dans les flux temps réel.
Metadata
improvementP1nextSMediumMediumEvidence
Files
First slice
Choisir un format unique (RFC3339 UTC), corriger les écritures UPDATE et ajouter une migration de normalisation des valeurs existantes.