Skip to content

fix(memory): return actual deleted count in AsyncSQLAlchemyMemory#1539

Open
Ricardo-M-L wants to merge 2 commits intoagentscope-ai:mainfrom
Ricardo-M-L:agentscope-fix-memory
Open

fix(memory): return actual deleted count in AsyncSQLAlchemyMemory#1539
Ricardo-M-L wants to merge 2 commits intoagentscope-ai:mainfrom
Ricardo-M-L:agentscope-fix-memory

Conversation

@Ricardo-M-L
Copy link
Copy Markdown
Contributor

Summary

Return actual deleted count in AsyncSQLAlchemyMemory instead of always returning a fixed value.

🤖 Generated with Claude Code

Ricardo-M-L and others added 2 commits April 27, 2026 12:23
When content blocks have a text field set to None (e.g., {"text": None}),
the code would crash with a TypeError when calling str.join(). This change
uses .get("text") instead of direct indexing to safely handle cases where
text is None or missing.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The delete() and delete_by_mark() methods were returning the number of
message IDs provided rather than the actual number of messages deleted.
This could cause issues in code that relies on the return value to
determine how many messages were actually removed. Now we use
result.rowcount to return the actual count from the database.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant