LightDB v0.0.2 has been released
Repository
https://github.com/ety001/steem-lightdb
What is the project about?
LightDB is another database service and solution for Steem and is based on Mysql.
LightDB will focus on the social data, not all data of Steem, such as users, comments and votes.
That's why I call it light.
LightDB also gives an easy way to deploy by docker.
New Features
- Rewrite all the block cache layer and improve the sync speed.
- Restructure database.
- Finish all transfer scripts.
Proof of work
https://github.com/ety001/steem-lightdb/pull/3
It's a nice beginning. You did well starting with a lightDB as some data are a nightmare to collect (I'm thinking of all the data related to finance)
A few remarks:
Your PR is huge, way too huge. The aim of a pull request is to write a functionality that will be reviewed by someone. Here you basically wrote your entire project. Commit on the master branch you have the same effect.
How do you deal with post modification ?
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
The bad data causes a huge PR. I have to test again and again. :(
Just to nitpick, a PR is not always made so someone else can review it. It is often made on single developer projects to mark major changes in development and so the process can easily be reversed.
Hardly any single developer project is getting PR reviews. It's nice Utopian kind of reviews them a little, but IMO, that is way out of scope of the Utopian project anyway.
Yeah, you're right. I agree one PR needs small as possible and focus on a single feature.
However, the disgusting data made me stuck and deepin quagmire of development. Therefore, in order to shorten the development time, I did not follow the rules.
Can you convert your timestamps to SQL format in the database? e.g. 2018-06-22 00:44:09
I think saving as integer will decrease the storage use. On the other hand the integer timestamp is easy to use in PHP code.
True. However I often interact with databases using UI clients, it's easier to look at human readable dates than unix timestamps 😉
lol
MySQL is a weak, you can use e.g. postgresql
During the development, I found that MySQL does really not fit Blockchain data.
MySQL was chosen because I am a php developer and MySQL and php are good partners.
I think the big problem of steem data is that the data consistency is relatively poor, and the format of the data is flexible. I prefer to select Nosql (such as MongoDB), if I rebuild this project.
But idea is not bad, all of steemit SQL projects has one problem - no elastic queries with metadata_json (e.g. equal, bigger/smaller operators)
Hey @ety001
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Contributing on Utopian
Learn how to contribute on our website or by watching this tutorial on Youtube.
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!