Expected Behavior
The timestamp should be accessible programmatically, like any other column in the chat memory table.
Current Behavior
When using JdbcChatMemoryRepository, all the details stored in the table spring_ai_chat_memory for every chat are accessible via the Message object, except for the timestamp column. This restricts UI/Chatbot-based applications from displaying the actual timestamp of every chat message. It also restricts one to sort old messages chronologically in any order. Another problem is the implementation of a standard data retention policy for chats.
It forces one to manually maintain another metadata table, causing unnecessary performance overhead and complexity.