-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MySql scheme incorrect. #24
Comments
What version of MySQL are you using? In my (limited) testing with 10.6.4-MariaDB using text on UNIQUE fields seem to work fine. For the service file: Do you refer to the one created by the installation script? (https://github.com/robske110/IDDataLogger/blob/master/docs/install.sh#L30-L46) |
varchar 64 should work fine yes. I can probably try on a fresh database if you update the code. Maybe just make a remark "(change pgsql to mysql if needed)". I would expect the service file to be able to depend on or the other in the same file, but I would not know how. |
Ok thanks and can you check what your MySQL server version is? |
ii mariadb-client-10.3 1:10.3.29-0+deb10u1 amd64 MariaDB database client binaries |
Hi,
You can't make a text field Unique (= key) without giving the key length. (authKey)
12:18:32.443773 [CRITICAL] PDOException: "SQLSTATE[42000]: Syntax error or access violation: 1170 BLOB/TEXT column 'authKey' used in key specification without a key length" (42000) in "[snip]Main.php" at line 82
And the service file could possible not only sheck for postgress but alternatively for mysql.
The text was updated successfully, but these errors were encountered: