What types of changes does your code introduce to ether_sql?
Put an x in the boxes that apply
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Explain your changes
Added a new table meta_info which will contain meta information about the sql table. Currently added a column last_uploaded_block to get the last uploaded block.
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
Types of changes
What types of changes does your code introduce to ether_sql? Put an
xin the boxes that applyExplain your changes
Added a new table
meta_infowhich will contain meta information about the sql table. Currently added a columnlast_uploaded_blockto get the last uploaded block.Does this close any currently open issues? https://github.com/analyseether/ether_sql/issues/18
Checklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Any relevant logs, error output, etc?
Not related to this PR but saw a strange bug have logged it here: https://github.com/analyseether/ether_sql/issues/31
Where has this been tested?
Operating System: Ubuntu 16.04
Node: Infura