fix JdbcChatMemoryRepository to support developer message

Signed-off-by: Andres da Silva Santos <[email protected]>

Author: andresssantos

memory/spring-ai-model-chat-memory-jdbc/src/main/java/org/springframework/ai/chat/memory/jdbc/JdbcChatMemoryRepository.java

@@ -30,6 +30,7 @@
 import org.springframework.ai.chat.messages.Message;
 import org.springframework.ai.chat.messages.MessageType;
 import org.springframework.ai.chat.messages.SystemMessage;
+import org.springframework.ai.chat.messages.DeveloperMessage;
 import org.springframework.ai.chat.messages.ToolResponseMessage;
 import org.springframework.ai.chat.messages.UserMessage;
 import org.springframework.jdbc.core.BatchPreparedStatementSetter;
@@ -129,6 +130,7 @@ public Message mapRow(ResultSet rs, int i) throws SQLException {
 				case USER -> new UserMessage(content);
 				case ASSISTANT -> new AssistantMessage(content);
 				case SYSTEM -> new SystemMessage(content);
+				case DEVELOPER -> new DeveloperMessage(content);
 				// The content is always stored empty for ToolResponseMessages.
 				// If we want to capture the actual content, we need to extend
 				// AddBatchPreparedStatement to support it.

memory/spring-ai-model-chat-memory-jdbc/src/test/java/org/springframework/ai/chat/memory/jdbc/JdbcChatMemoryRepositoryPostgresqlIT.java

@@ -24,6 +24,7 @@
 import org.springframework.ai.chat.messages.MessageType;
 import org.springframework.ai.chat.messages.AssistantMessage;
 import org.springframework.ai.chat.messages.SystemMessage;
+import org.springframework.ai.chat.messages.DeveloperMessage;
 import org.springframework.ai.chat.messages.UserMessage;
 import org.springframework.beans.factory.annotation.Autowired;
 import org.springframework.boot.SpringBootConfiguration;
@@ -72,6 +73,7 @@ void saveMessagesSingleMessage(String content, MessageType messageType) {
 			case ASSISTANT -> new AssistantMessage(content + " - " + conversationId);
 			case USER -> new UserMessage(content + " - " + conversationId);
 			case SYSTEM -> new SystemMessage(content + " - " + conversationId);
+			case DEVELOPER -> new DeveloperMessage(content + " - " + conversationId);
 			default -> throw new IllegalArgumentException("Type not supported: " + messageType);
 		};