You should definitively consider using mongodb instead of a sql database:
- it stores json, so you can directly store the outputs of the bitcoind commands
- it's highly scalable (sharding and replica sets)
- it's very easy to use
- it can store UGE amounts of data and still perform very well on queries
- sql databases aren't a great thing because of the number of "sub tables" needed (to store the inputs/outputs of the transactions, etc.)
Topic: SQL for storing blockchain transactions (Read 1519 times)
because we can't query the blockchain for certain data. we need to store it in our own DB.
Calls like getRawTransaction, such as computing an addresses balance etc
Calls like getRawTransaction, such as computing an addresses balance etc
The block chain essentially is a database of all transactions. Why would you need another database?
Is anybody saving the blockchain transactions.
Does anyone have a SQL schema they want to share?
Or can anyone help with pointers
Does anyone have a SQL schema they want to share?
Or can anyone help with pointers
Jump to: