Jude Nelson 9d64dc091a do either an INSERT or an UPDATE, depending on whether or not we're preorder/registering or re-preordering/registering. Also, tighten the input validation logic to ensure that each state-create and state-transition op data contains both the history ID (name or namespace) as well as the block number (i.e. all column data that goes into the table's primary key)

2018-01-13 22:52:53 -05:00

..

__init__.py

the new database schema no longer requires us to fetch and store prior name histories in our check() decorators. Remove the ancilliary code that they had been using to do this.

2018-01-12 18:31:45 -05:00

db.py

do either an INSERT or an UPDATE, depending on whether or not we're preorder/registering or re-preordering/registering. Also, tighten the input validation logic to ensure that each state-create and state-transition op data contains both the history ID (name or namespace) as well as the block number (i.e. all column data that goes into the table's primary key)

2018-01-13 22:52:53 -05:00

namedb.py

rework the BlockstackDB class to rely on virtualchain-provided database functionality (such as getting a block's ops hash), and rework the methods to use the new queries. In particular, history replaying is no longer necessary since we store all snapshots of all name records now.

2018-01-12 18:27:02 -05:00

virtualchain_hooks.py

update virtualchain_hooks (the virtualchain implementation) to adhere to the new StateEngine standards in virtualchain 0.18. In particular:

2018-01-12 18:28:06 -05:00