Himanshu Khairajani e86a0201ab

Fix #25645: MySQL timestamp precision for tag_usage.appliedAt (#25643) ...

* Fix MySQL timestamp precision for tag_usage.appliedAt

MySQL's TIMESTAMP type defaults to second precision, while PostgreSQL
returns microsecond precision. This causes _normalize_datetime_strings
in the Python ingestion client to produce spurious appliedAt diffs in
JSON patches, which then fail with "Failed to convert JsonValue to
target class" during deserialization in JsonUtils.applyPatch().

Upgrade appliedAt to TIMESTAMP(6) to match PostgreSQL behavior and
eliminate the spurious patch diffs.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* Add 1.11.8 migration for MySQL appliedAt timestamp precision

Backport the TIMESTAMP(6) fix to the 1.11.x release line so existing
deployments on 1.11.x pick up the fix without requiring a 1.12.0 upgrade.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-30 12:46:19 +01:00

..

migrations

Fix #25645: MySQL timestamp precision for tag_usage.appliedAt (#25643)

2026-01-30 12:46:19 +01:00

schema

Deprecate Flyway and use Native migrations (#12865)

2023-08-17 14:39:05 -07:00