You are viewing a single comment's thread from:

RE: Proposal: Public Hivemind SQL service

in #proposal5 years ago (edited)

Yes, it will be the same except Hivemind doesn't store whole blockchain data like SteemSQL. Instead, it focuses on social aspects like votes, comments, posts, resteems, relationships. (ignore, follow, etc.)

In the future, communities data is also planned to store at Hivemind.

Sort:  

Sounds great! Looking forward to be one of the first to test :) You already have my witness vote and I will support this proposal.

It is available with a subscription fee.

Post includes a Q/A section explains the main difference.

I run my own hivemind node as well as pay for SteemSQL access. I find that hivemind is often better for querying certain things as compared to SteemSQL.

In some cases, results come back faster in hivemind because of how the indices are arranged.

One of the major benefits of hivemind is how tags are tracked. If you’re doing content specific queries, it’s usually better to use hivemind.

I have used SteemSQL, it is awesome. However, it is not affordable for an average user, especially with the current Steem prices.

Building a free alternative for users and independent developers should be welcomed.

:)

Then just don’t vote. You’re twisting words, I really dont have time for that usual wehmoen toxicity.

Both Hivemind and SteemSQL interpret the blockchain differently. A really good example of how some Hivemind queries are useful over SteemSQL is doing tag queries. With Hivemind, you can do a query that matches posts that have all tags specified. With SteemSQL, this is difficult.

When I say "all tags specified" I mean that you want posts that match "tag a" and "tag b" as opposed to "tag a" or "tag b".

This is possible in Hivemind because tags are a dedicated table, so doing that kind of query is somewhat trivial. With SteemSQL, you could probably achieve it with sub-selects and temporary tables, but I haven't needed to look into it.

Some more examples: Hivemind Queries