Shouldn't a odbc jdbc jconnect or equivalent be totally transparent for the
consensus code? I mean, the client would write or store the data communicating
to the driver provided by the vendor. Using the schema bitcoin suggests adapted
to many different vendors (one table schema for Oracle, other
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
Hello,
I have been working on database engineering for many years and there are
some things i don't understand very well about how bitcoin architecture
works. I have not written here because i would not like to disturb
development with yet another of those far to implement ideas that does
not
