Repository navigation
Fix #641 - Add VECTOR data type and VECTOR INDEX support - #651
predictor2718 wants to merge 2 commits into
Conversation
Signed-off-by: Nicolai Ehrhardt <245527909+predictor2718@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 5.11.x #651 +/- ##
=========================================
Coverage 96.92% 96.92%
Complexity 2316 2316
=========================================
Files 71 71
Lines 5110 5110
=========================================
Hits 4953 4953
Misses 157 157
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Nicolai Ehrhardt <245527909+predictor2718@users.noreply.github.com>
|
MariaDB also prints the vector index options in VECTOR KEY `v` (`v`) `M`='8' `DISTANCE`='cosine'With this branch, 'M' => [7, 'var='],
'DISTANCE' => [8, 'var='],The quoted form also needs backquoted option names to be accepted, see #644. Docs: https://mariadb.com/docs/server/reference/sql-structure/vectors/create-table-with-vectors |
Summary
VECTORas a reserved keyword withFLAG_KEYWORD_DATA_TYPEin MySQL 9.0-9.3 contextsVECTORas a reserved keyword withFLAG_KEYWORD_DATA_TYPEin MariaDB 11.7-12.1 contextsVECTOR INDEXandVECTOR KEYas composed key keywords in all affected contextsVECTOR(5)triggered "Unrecognized data type" andVECTOR INDEXwas parsed as a column definitionFixes #641.