Overview
Migrating ethopy to datajoint v2 (≥2.0.0) requires infrastructure upgrades before it can be completed. See the official migration guide:
https://docs.datajoint.com/how-to/migrate-to-v20/
What needs to happen
- Upgrade the database server to MySQL 8.0+
- Configure character encoding:
utf8mb4 charset with utf8mb4_bin collation
- Upgrade Python environment to 3.10+
- Merge branch
fix/datajoint-v2-compatibility which contains the ethopy-side migration changes and is ready — only blocked by the above
Note on MariaDB
datajoint v2 requires MySQL 8.0+ specifically. MariaDB is not supported, it lacks the EXPRESSION column in information_schema.statistics used by datajoint v2's index introspection.
Overview
Migrating ethopy to datajoint v2 (≥2.0.0) requires infrastructure upgrades before it can be completed. See the official migration guide:
https://docs.datajoint.com/how-to/migrate-to-v20/
What needs to happen
utf8mb4charset withutf8mb4_bincollationfix/datajoint-v2-compatibilitywhich contains the ethopy-side migration changes and is ready — only blocked by the aboveNote on MariaDB
datajoint v2 requires MySQL 8.0+ specifically. MariaDB is not supported, it lacks the
EXPRESSIONcolumn ininformation_schema.statisticsused by datajoint v2's index introspection.