-
Notifications
You must be signed in to change notification settings - Fork 66
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge #1180: Save transactions in database
bf1e90e sqlite: merge two migration tests (jp1ac4) e883675 sqlite: add a unit test for migration between v4 and v5 (Antoine Poinsot) af5fddf commands: use database for TxGetter (jp1ac4) a86d12d commands: get wallet transactions from db (jp1ac4) afa6a51 poller: save transactions in database (jp1ac4) ba4c819 sqlite: separate DB migration from constructor (Antoine Poinsot) 50e7ffa lib: setup the connection to bitcoind before the connection to SQLite. (Antoine Poinsot) Pull request description: This is the first step of #56 (comment). The poller will now save transactions in our own database. These transactions are selected based on the deposit and spend transactions of coins. Only the txid and transaction itself are saved, with the corresponding block height and time taken from the coins table. In a couple of follow-up commits, I've replaced some RPC calls to bitcoind with DB queries. ACKs for top commit: darosior: re-ACK bf1e90e Tree-SHA512: a1d0a6381efe307655b94a3ff257c58e4d921e98a7fa79e5c9f80016c19df761b10266d4122cb290b78424c5e2acefc163683fcfc948950e3c838e39ba31ba57
- Loading branch information
Showing
8 changed files
with
1,039 additions
and
316 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.