📅 Original date posted:2015-10-29
📝 Original message:Why not allow two options:
1/ a default RocksDB/SQLite/LevelDB (whatever is decided)
2/ alternative provide instructions for connection to any other rdbms
using odbc or jdbc.
Why not allowing async disk writes or incredibly fast database systems
if someone wants to have a node in a very fast datacenter or connected
with their existing leveraged dataservers. It is the traditional
approach to just use the open standard for database connectivity.
Any person or any organization would just need to have one machine with
their bitcoin node with a rdbms client installed (SAP Sybase client, or
oracle client, or microsoft). The bitcoin node would just store their
data using the odbc/jdbc protocol on ANY rdbms installed anywhere in
their organization (other machine or the same). They would just need to
issue a "create table" with a very simple table structure and they would
benefit from async and indexes and using their already licensed, and
configured system of their choosing, with bitcoin information being
available to thousands of software packages and available aswell to
thousands of programmers that work with rdbms and not just "RocksDB" or
some obscure database system.
Why not "outsource" totally that data management part to the already
existing with decades of experience database world. People would be able
to create incredibly easy bitcoin statistics/graphs/analisys with
existing software packages (hey even excel or libreoffice like) or
connect bitcoin data to their own sources and if so they chose analyze
bitcoin data on a datawarehouse or any imaginable approach. Of course
every transaction would be have to do through the bitcoin node and only
the data management would be on rdbms side.
telemaco [ARCHIVE] /
npub1vf…lg63q
2023-06-07 17:43:54
in reply to nevent1q…7wy3
Author Public Key
npub1vfzjp8quyqspa3s9z34y0552e90j7jru2vycrtzhl78q4mffgwlselg63qSeen on
wss://relay.noswhere.comPublished at
2023-06-07 17:43:54Event JSON
{
"id": "df648de764a376b4d1022d35266c092277cd22b46636658237b7441d2c7a6195",
"pubkey": "6245209c1c20201ec605146a47d28ac95f2f487c530981ac57ff8e0aed2943bf",
"created_at": 1686159834,
"kind": 1,
"tags": [
[
"e",
"09f07bc0e1ba48805727ba44deb034dc283bfadbc39b90714e52ddd0cad07414",
"",
"root"
],
[
"e",
"a3c52d7d50d021e4e4c0ac4ba821d6a7de8823c3d8feb49515e74378631e3fef",
"",
"reply"
],
[
"p",
"dcb947d818dbfd7cf0baf26c0d5eb606b5a32336c5483fb53e05146315833ca7"
]
],
"content": "📅 Original date posted:2015-10-29\n📝 Original message:Why not allow two options:\n\n1/ a default RocksDB/SQLite/LevelDB (whatever is decided)\n2/ alternative provide instructions for connection to any other rdbms \nusing odbc or jdbc.\n\nWhy not allowing async disk writes or incredibly fast database systems \nif someone wants to have a node in a very fast datacenter or connected \nwith their existing leveraged dataservers. It is the traditional \napproach to just use the open standard for database connectivity.\n\nAny person or any organization would just need to have one machine with \ntheir bitcoin node with a rdbms client installed (SAP Sybase client, or \noracle client, or microsoft). The bitcoin node would just store their \ndata using the odbc/jdbc protocol on ANY rdbms installed anywhere in \ntheir organization (other machine or the same). They would just need to \nissue a \"create table\" with a very simple table structure and they would \nbenefit from async and indexes and using their already licensed, and \nconfigured system of their choosing, with bitcoin information being \navailable to thousands of software packages and available aswell to \nthousands of programmers that work with rdbms and not just \"RocksDB\" or \nsome obscure database system.\n\nWhy not \"outsource\" totally that data management part to the already \nexisting with decades of experience database world. People would be able \nto create incredibly easy bitcoin statistics/graphs/analisys with \nexisting software packages (hey even excel or libreoffice like) or \nconnect bitcoin data to their own sources and if so they chose analyze \nbitcoin data on a datawarehouse or any imaginable approach. Of course \nevery transaction would be have to do through the bitcoin node and only \nthe data management would be on rdbms side.",
"sig": "46fb7ef06f8f737204ca2694875ccf273300647b6b367eeee9bcc15b997f78bd0b29a4e4cdc1355d64d06e402825d78dd5f82a34116c39ba8ac7c4b441bb19c1"
}