Resolve all Chronicle issues in MySQL #33
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
datetime
fields filled automatically by MySQL.ERROR 1048 (23000): Column 'prevhash' cannot be null
. Resolved at database level by swapping foreign key ruleprevhash
withcurrhash
.datetime
fields. [Not-Resolved]Thanks