I did not indicate this in the previous posts but SteemSQL Wrapper has a limit for records to return, meaning that you cannot write something like SELECT * FROM Comments and get 21,166,246 rows (but please, even do not try doing it, especially on your own SteemSQL connection).
Initially, SteemSQL Wrapper had a hardcoded limit in 5k rows but today I published changes which allow you to change it. By default, it is set up on 500 rows. But you can easily change it — just move the slider or enter your number in the input field. Right now it still has constraints — you can set up a limit only up to 5k.
I am still not sure which max constraint will be the best because in many cases users can hurt SteemSQL or even themselves. For example, if a user will forget to write TOP in a base query (like in my above example) then their browser in the most cases will be freeze or even will collapse.
Also, my project is more for small data because right now you cannot do a serious analysis with dozens of thousands of rows — SteemSQL Wrapper just does not have any tools for this. Anyway, I would like to hear your feedback and any suggestions about this constraint.
P.S. Also, I think that anyone who has an interest in SteemSQL Wrapper or SteemSQL should read (and upvote/resteem) the recent post of 
Posted on Utopian.io - Rewarding Open Source Contributors