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.

Sign up for GitHub

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

Jump to bottom

SQL Schema alters accounts.creation type and it throws errors when using the Coin Store #30

Open

1 task done

macvirii opened this issue Nov 19, 2023 · 1 comment

Labels

Status: Pending Test

macvirii commented Nov 19, 2023

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

I agree to follow this project's Code of Conduct

github-actions bot added the Status: Pending Test label

Author

macvirii commented Nov 19, 2023

Account creation then works by using the unix_timestamp as default:

creation int(11) NOT NULL DEFAULT unix_timestamp(),

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment