Skip to content

SQL, API, and rate-limiting improvements#11

Open
rtucker wants to merge 3 commits into
mbilokonsky:masterfrom
vulpineclub:sql-improvements
Open

SQL, API, and rate-limiting improvements#11
rtucker wants to merge 3 commits into
mbilokonsky:masterfrom
vulpineclub:sql-improvements

Conversation

@rtucker

@rtucker rtucker commented Jun 27, 2017

Copy link
Copy Markdown

Instead of caching, uses a subquery to determine if the toot has already been boosted by ourself.

Snags our current account ID from the API so we can do the aforementioned determination.

Also puts a LIMIT clause on the query so that we only boost a certain number of toots per run (default: 2). This particular adjustment was courtesy of me forgetting to restart Ambassador after a reboot...

This pull request is a bit of a congealed mess. I, or someone else, could split it into a couple distinct patches without too much effort I think.

rtucker added 2 commits June 27, 2017 00:30
We can see if we've already boosted a toot via the database, so
it is possible to have postgres take care of this for us.
I used ceil() to make things a little cleaner-looking, but it
shifted the number of faves required up by 1.  (e.g. if the avg
is 3.141, this patch returns the fave threshold back to 4)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant