From: Petr Praus <petr@praus.net>
To: Marko Otbalkana <marko.otbalkana@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Blockchain alternative storage
Date: Wed, 5 Jun 2013 20:49:22 -0500 [thread overview]
Message-ID: <CACezXZ-KecLVkw3j2fE7ZmXkjVG4ZjdNu_rExo_xDhcbrWCnGQ@mail.gmail.com> (raw)
In-Reply-To: <CALG7eYpKj9Ev2a1PZ7qsiqsazS4pHTPiGF22r64=s1buWm2aLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
BitcoinJ is storing parsed blocks (not the whole chunks of bytes) in H2, an
embedded SQL database for Java.
On 5 June 2013 19:53, Marko Otbalkana <marko.otbalkana@gmail.com> wrote:
> Could anyone point me to work/project(s) related to storing the block
> chain in a database, like PostgreSQL, MySQL? How about any tools that can
> read the block chain from the Satoshi client and convert it into different
> formats?
>
> Thanks,
> -Marko
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 1623 bytes --]
next prev parent reply other threads:[~2013-06-06 2:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 0:53 [Bitcoin-development] Blockchain alternative storage Marko Otbalkana
2013-06-06 1:17 ` Patrick Strateman
2013-06-06 1:49 ` Petr Praus [this message]
2013-06-06 8:20 ` Jouke Hofman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACezXZ-KecLVkw3j2fE7ZmXkjVG4ZjdNu_rExo_xDhcbrWCnGQ@mail.gmail.com \
--to=petr@praus.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=marko.otbalkana@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox