Fix: MySQL/MariaDB TIMESTAMP precision for message ordering (#3442)

Fixes #3442

Signed-off-by: Seungwon Lee <[email protected]>

Author: seungwone

memory/repository/spring-ai-model-chat-memory-repository-jdbc/src/main/resources/org/springframework/ai/chat/memory/repository/jdbc/schema-mariadb.sql

@@ -2,7 +2,7 @@ CREATE TABLE IF NOT EXISTS SPRING_AI_CHAT_MEMORY (
     conversation_id VARCHAR(36) NOT NULL,
     content TEXT NOT NULL,
     type VARCHAR(10) NOT NULL,
-    `timestamp` TIMESTAMP NOT NULL,
+    `timestamp` TIMESTAMP(3) NOT NULL,
     CONSTRAINT TYPE_CHECK CHECK (type IN ('USER', 'ASSISTANT', 'SYSTEM', 'TOOL'))
 );
 

memory/repository/spring-ai-model-chat-memory-repository-jdbc/src/main/resources/org/springframework/ai/chat/memory/repository/jdbc/schema-mysql.sql

@@ -2,7 +2,7 @@ CREATE TABLE IF NOT EXISTS SPRING_AI_CHAT_MEMORY (
     `conversation_id` VARCHAR(36) NOT NULL,
     `content` TEXT NOT NULL,
     `type` ENUM('USER', 'ASSISTANT', 'SYSTEM', 'TOOL') NOT NULL,
-    `timestamp` TIMESTAMP NOT NULL,
+    `timestamp` TIMESTAMP(3) NOT NULL,
 
     INDEX `SPRING_AI_CHAT_MEMORY_CONVERSATION_ID_TIMESTAMP_IDX` (`conversation_id`, `timestamp`)
 );