We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
High
App
Linux
Chrome
The current schema interferes with the expected data type from canary.
The field accounts.creation is altered for timestamp but as we see on the following, it expects a int(11) epoch date time.
The canary code is on Line 42 of account_repository_db.cpp , and it ends up with errors on every store transaction. https://github.com/opentibiabr/canary/blob/264efd5352097ce330d80024121399c4dd2666e3/src/account/account_repository_db.cpp#L42
Changing back the table for int(11) fixes the server errors.
The text was updated successfully, but these errors were encountered:
Account creation then works by using the unix_timestamp as default:
creation int(11) NOT NULL DEFAULT unix_timestamp(),
creation
Sorry, something went wrong.
No branches or pull requests
Priority
High
Area
App
What OS are you seeing the problem on?
Linux
Browser
Chrome
What happened?
The current schema interferes with the expected data type from canary.
The field accounts.creation is altered for timestamp but as we see on the following, it expects a int(11) epoch date time.
The canary code is on Line 42 of account_repository_db.cpp , and it ends up with errors on every store transaction.
https://github.com/opentibiabr/canary/blob/264efd5352097ce330d80024121399c4dd2666e3/src/account/account_repository_db.cpp#L42
Changing back the table for int(11) fixes the server errors.
Code of Conduct
The text was updated successfully, but these errors were encountered: