From a89daf3d4337a285406aa6651c36276d8994b0e1 Mon Sep 17 00:00:00 2001 From: root Date: Fri, 20 Feb 2026 20:56:13 +0000 Subject: [PATCH] Fix CURRENT_TIMESTAMP not normalized to CURRENT_TIMESTAMP(3) in migrations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- app/RSpade/Core/Database/SqlQueryTransformer.php | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/app/RSpade/Core/Database/SqlQueryTransformer.php b/app/RSpade/Core/Database/SqlQueryTransformer.php index 7f2d796cc..0c0b54e79 100644 --- a/app/RSpade/Core/Database/SqlQueryTransformer.php +++ b/app/RSpade/Core/Database/SqlQueryTransformer.php @@ -474,6 +474,7 @@ class SqlQueryTransformer * Transform datetime column types to include millisecond precision * * Converts: TIMESTAMP → TIMESTAMP(3) + * Converts: CURRENT_TIMESTAMP → CURRENT_TIMESTAMP(3) * Converts: DATETIME → DATETIME(3) * * This ensures datetime columns have millisecond precision from the start, @@ -486,12 +487,20 @@ class SqlQueryTransformer { // TIMESTAMP without precision → TIMESTAMP(3) // Don't match if already has precision: TIMESTAMP(3), TIMESTAMP(6) + // Don't match CURRENT_TIMESTAMP (handled separately below) $query = preg_replace( - '/\bTIMESTAMP\b(?!\s*\()/i', + '/(?