Benjamin Gaussorgues
Benjamin Gaussorgues
Hello, I got the same problem on MySQL 8. ```sql ALTER TABLE `django_etebase_collectiontype` ADD CONSTRAINT `django_etebase_collectiontype_uid_ba9e127e_uniq` UNIQUE (`uid`); ``` ``` ERROR 1170 (42000): BLOB/TEXT column 'uid' used in key specification...
Yes,I think so. I was able to launch service and create an account just after.
Sorry, same error… On a fresh install, I got the following: ``` > ./manage.py migrate [...] Applying django_etebase.0031_auto_20201013_1336... OK Applying django_etebase.0032_auto_20201013_1409...Traceback (most recent call last): File "/opt/etebase/.venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in...
Arf, sorry, I still have the same error. I am wondering why Django creates a `LONGBLOB`, I think it should be a `VARBINARY`. Any idea how to do that?
Yes, MySQL supports index (unique or not) on `VARBINARY`. If I understood correctly MySQL can only index first bytes of a `(LONG)BLOB` so it cannot creates a `UNIQUE` index. It...
For anyone hitting this bug, here is a temporary workaround: - Run all possible patchs as documented: ```bash ./manage.py migrate # Fail on patch 32 ``` - Open MySQL with...
Done in another PR
The fix has been merged in `master`. The backport for `stable28` is ready: https://github.com/nextcloud/server/pull/43833 Any test is welcome :)
https://github.com/nextcloud/server/pull/43833 wasn't included in 28.0.3. It was merged too late since second RC was already out.
I would also vote for a setup check :)