<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated></updated>
  <generator>https://nostr.ae</generator>

  <title>Nostr notes by </title>
  <author>
    <name></name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://nostr.ae/npub1vfzjp8quyqspa3s9z34y0552e90j7jru2vycrtzhl78q4mffgwlselg63q.rss" />
  <link href="https://nostr.ae/npub1vfzjp8quyqspa3s9z34y0552e90j7jru2vycrtzhl78q4mffgwlselg63q" />
  <id>https://nostr.ae/npub1vfzjp8quyqspa3s9z34y0552e90j7jru2vycrtzhl78q4mffgwlselg63q</id>
  <icon></icon>
  <logo></logo>




  <entry>
    <id>https://nostr.ae/nevent1qqsd7eyduaj2xa456ypz6dfxdsyjya7dy26xvdn9sgmmw3qa93axr9gzyp3y2gyursszq8kxq52x537j3ty47t6g03fsnqdv2llcuzhd99pm77hc8x5</id>
    
      <title type="html">📅 Original date posted:2015-10-29 📝 Original message:Why ...</title>
    
    <link rel="alternate" href="https://nostr.ae/nevent1qqsd7eyduaj2xa456ypz6dfxdsyjya7dy26xvdn9sgmmw3qa93axr9gzyp3y2gyursszq8kxq52x537j3ty47t6g03fsnqdv2llcuzhd99pm77hc8x5" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqs283fd04gdqg0yunq2cjagy8t20h5gy0pa3l45j527wsmcvv0rlmc8x7wy3&#39;&gt;nevent1q…7wy3&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;📅 Original date posted:2015-10-29&lt;br/&gt;📝 Original message:Why not allow two options:&lt;br/&gt;&lt;br/&gt;1/ a default RocksDB/SQLite/LevelDB (whatever is decided)&lt;br/&gt;2/ alternative provide instructions for connection to any other rdbms &lt;br/&gt;using odbc or jdbc.&lt;br/&gt;&lt;br/&gt;Why not allowing async disk writes or incredibly fast database systems &lt;br/&gt;if someone wants to have a node in a very fast datacenter or connected &lt;br/&gt;with their existing leveraged dataservers. It is the traditional &lt;br/&gt;approach to just use the open standard for database connectivity.&lt;br/&gt;&lt;br/&gt;Any person or any organization would just need to have one machine with &lt;br/&gt;their bitcoin node with a rdbms client installed (SAP Sybase client, or &lt;br/&gt;oracle client, or microsoft). The bitcoin node would just store their &lt;br/&gt;data using the odbc/jdbc protocol on ANY rdbms installed anywhere in &lt;br/&gt;their organization (other machine or the same). They would just need to &lt;br/&gt;issue a &amp;#34;create table&amp;#34; with a very simple table structure and they would &lt;br/&gt;benefit from async and indexes and using their already licensed, and &lt;br/&gt;configured system of their choosing, with bitcoin information being &lt;br/&gt;available to thousands of software packages and available aswell to &lt;br/&gt;thousands of programmers that work with rdbms and not just &amp;#34;RocksDB&amp;#34; or &lt;br/&gt;some obscure database system.&lt;br/&gt;&lt;br/&gt;Why not &amp;#34;outsource&amp;#34; totally that data management part to the already &lt;br/&gt;existing with decades of experience database world. People would be able &lt;br/&gt;to create incredibly easy bitcoin statistics/graphs/analisys with &lt;br/&gt;existing software packages (hey even excel or libreoffice like) or &lt;br/&gt;connect bitcoin data to their own sources and if so they chose analyze &lt;br/&gt;bitcoin data on a datawarehouse or any imaginable approach. Of course &lt;br/&gt;every transaction would be have to do through the bitcoin node and only &lt;br/&gt;the data management would be on rdbms side.
    </content>
    <updated>2023-06-07T19:43:54&#43;02:00</updated>
  </entry>

</feed>