feat(tools_api): add upsert support to create_tool_from_schema #45
+78
−35
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.
create_tool_from_schema now updates existing tools instead of failing on unique constraint.
Problem:
When calling create_tool_from_schema with an existing tool code, it failed with:
ORA-00001: unique constraint (KS.UC_AI_TOOLS_UK) violated on table KS.UC_AI_TOOLS columns (CODE)Solution:
Check if tool with same code exists before insert
If exists: update the tool record, delete and recreate parameters and tags
If not exists: create new tool as before
Use Case:
Users may call uc_ai_tools_api.create_tool_from_schema multiple times to quickly update parameter values, tool instructions, or other tool configuration without needing to manually delete the tool first.
Changes:
uc_ai_tools_api.pkb: Added upsert logic to create_tool_from_schema
uc_ai_tools_api.pks: Updated documentation to reflect new behavior