Skip to content
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

Resolve all Chronicle issues in MySQL #33

Closed
wants to merge 4 commits into from

Conversation

vzool
Copy link
Contributor

@vzool vzool commented Oct 20, 2018

Hi,

I tested Chronicle in MySQL connection and I have some issues, I resolved two of them. But, there are many more needs to collaboration with some guidance.

The current known issues are:

  • issue mentioned here SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value #32. Resolved by made datetime fields filled automatically by MySQL.
  • issue ERROR 1048 (23000): Column 'prevhash' cannot be null. Resolved at database level by swapping foreign key rule prevhash with currhash.
  • When Chronicle use MySQL should ignore values for datetime fields. [Not-Resolved]
  • Revise replica functions. [Not-Resolved]

Thanks

@vzool
Copy link
Contributor Author

vzool commented Oct 20, 2018

screen shot 2018-10-20 at 2 20 31 pm

Publish data is working now after I commented this line and the Sapient response has an error:

No valid signature given for this HTTP response

🤔

@vzool
Copy link
Contributor Author

vzool commented Oct 20, 2018

screen shot 2018-10-20 at 4 46 36 pm

Lock UPDATE for all fields on the chain, make it immutable 🤓

@vzool
Copy link
Contributor Author

vzool commented Oct 21, 2018

I messed things up, I will close this and create new clear one.

@vzool vzool closed this Oct 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant