test: add comprehensive special character tests for all fields

[NTLx]

Summary

Addressing issue #133.
Added a new unit test file tests/unit_tests/test_special_characters.py to verify that the client correctly handles special characters in:

• Collection names (validation)
• IDs (escaping and binary casting)
• Documents (escaping)
• Metadata (JSON serialization and escaping)

Tested scenarios include:

• SQL injection attempts
• Special syntax characters (newlines, null bytes, backslashes)
• Unicode characters (Chinese, Arabic, Hebrew, Emoji)
• Whitespace

Test plan

Ran the new tests locally using uv run pytest tests/unit_tests/test_special_characters.py -v.
All 4 tests passed.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Tests
  • Added unit tests verifying handling of special characters in IDs, document content, and metadata serialization.
  • Added tests to validate collection naming rules and proper error handling for invalid names.
  • Introduced mock testing support to simulate backend interactions and assert generated SQL and operations.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new unit test module that verifies handling of special characters in IDs, documents, metadata, and collection names. Introduces a MockClient subclass of BaseClient and TestSpecialCharacters with four tests validating SQL generation, escaping/serialization, and collection name validation.

Changes

Cohort / File(s)	Summary
Special characters tests tests/unit_tests/test_special_characters.py	Adds MockClient (subclass of BaseClient with a mocked executor) and TestSpecialCharacters (unittest.TestCase) containing tests for IDs with special characters (CAST ... AS BINARY), documents with special characters, metadata JSON serialization/escaping and INSERT SQL checks, and collection name validation via _validate_collection_name.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

Suggested reviewers

• hnwyllmm

Poem

🐰 I nibble on strings with cheer,

Quotes and slashes, never fear,
IDs and docs tucked safe at night,
Metadata twinkles, escaped just right,
Hopping through tests, I hold the light.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically summarizes the main change: adding comprehensive tests for special character handling across all fields (IDs, documents, metadata, collection names).
Docstring Coverage	✅ Passed	Docstring coverage is 94.12% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@tests/unit_tests/test_special_characters.py`:
- Around line 2-8: The tests in test_special_characters.py create variables
executed_sql and metadata_key_test but never assert anything; update the two
test methods to assert that the SQL and metadata strings contain properly
escaped fragments by using escape_string from pymysql.converters to compute
expected escaped values and comparing them to executed_sql and metadata_key_test
(e.g., assert expected in executed_sql and assert expected_meta in
metadata_key_test), which will both validate escaping behavior and eliminate the
F841 unused-variable warnings; reference the existing variables executed_sql,
metadata_key_test and the escape_string function to locate where to inject these
assertions.

[frostming]

Usually the project is installed when running the tests, so these are not necessary.

[NTLx]

Hi @hnwyllmm! This PR is now MERGEABLE with all CI checks passing.

Summary:

• Added comprehensive special character tests for IDs, documents, metadata, and collection names
• All unit and integration tests passing
• Docstring coverage at 94.12%

Ready for merge!