feat: Add tool_calls support to JdbcChatMemoryRepository #3343
+219
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR implements support for persisting
tool_calls
inJdbcChatMemoryRepository
to resolve issues with tool calling functionality in JDBC-based chat memory implementations.Issues Addressed
Fixes #3342 - Support persisting tool_calls in JdbcChatMemoryRepository
It can also serve as a preliminary step to fix the issues below:
#3339 - ToolResponseMessage results in null content, causing SQLIntegrityConstraintViolationException
Changes
Database Schema
tool_calls
column to all database schemas (PostgreSQL, MySQL, SQL Server, HSQLDB)JSONB
type with explicit::jsonb
castingTEXT
/LONGVARCHAR
for JSON storageImplementation
List<AssistantMessage.ToolCall>
to JSON on inserttool_calls
in SELECT and INSERT queriesDatabase Dialects Updated
PostgresChatMemoryRepositoryDialect
MysqlChatMemoryRepositoryDialect
SqlServerChatMemoryRepositoryDialect
HsqldbChatMemoryRepositoryDialect