fix: '\x00' Issue in Python SDK Precompiled SQL Inserts#3788
fix: '\x00' Issue in Python SDK Precompiled SQL Inserts#3788tobegit3hub merged 8 commits into4paradigm:mainfrom
Conversation
…t520100/OpenMLDB into fix/precompiled-sql-string-whitespace
SDK Test Report101 files ±0 101 suites ±0 2m 7s ⏱️ -6s Results for commit 4203da8. ± Comparison against base commit 42f9b89. This pull request removes 30 and adds 11 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3788 +/- ##
============================================
+ Coverage 40.28% 40.68% +0.39%
Complexity 658 658
============================================
Files 194 195 +1
Lines 11436 11514 +78
Branches 1380 1380
============================================
+ Hits 4607 4684 +77
- Misses 6525 6526 +1
Partials 304 304 ☔ View full report in Codecov by Sentry. |
Linux Test Report 56 files + 3 189 suites +129 1h 24m 8s ⏱️ + 56m 7s For more details on these failures, see this check. Results for commit 4203da8. ± Comparison against base commit 42f9b89. ♻️ This comment has been updated with latest results. |
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix
What is the current behavior? (You can also link to an open issue here)
After inserting data with precompiled SQL, when queried, certain fields have additional null characters ('\x00') appended at the end #3779
Resolve the issue of extra '\x00' characters in string fields when inserting data using precompiled SQL in the Python SDK.
What is the new behavior (if this is a feature change)?