RE: Additional endpoints for SteemPlus backend
Thank you for your contribution. @steemsql is not free anymore and thus we should be very careful in this as this potentially will make the API server a proxy between users and steemsql.
However, as I understand this, it is useful to separate logics from the presentation, as you are using the APIs in Chrome extension, thus intelligent users may view-source and get the API directly.
On here, line 86, you are missing a (NOLOCK) which might impose load to the steemsql server. And I am not sure this is the 'correct' way to get incoming delegation as you are making assumptions that the ID increases as the timestamp increases. You might want to look at alternative solution such as here
Need help? Write a ticket on https://support.utopian.io.
Chat with us on Discord.
Hey @justyy, thanks for your comment.
I have regular contacts with @stoodkev about his great SteemPlus Chrome add-on and its usage of SteemSQL. We already talked together about "proxy risk" of publicly exposing API and this something @stoodkev perfectly understand.
As explained in this post, the NOLOCK hint is no more required.
This is partially correct. ID indeed increase over time as it is an autonumber column. Anyway, should I implement non-linear blocks processing to improve performances, this assumption would become false.
Thanks for taking the time to help us improve these queries!