-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MySQL DB update issue #28
Comments
Another solution would be querying since a specific date time string if the Twitter API allows for this. This will allow the bot to function independent of individual tweets for anchor points (could be deleted). Also, instead of storing the last tweeted date in a database, we could just Tweet since |
We would want to find a way to not store the last seen ID anymore. Some way to query the twitter API and retweet every 10mins as usual. We can look at other Twitter bots for inspiration. |
closing to migrate issue to #31 |
Currently the bot will go down in the situation where the app fails to do an
UPDATE
on the MySQL database. At the very end of retweeting tweets, the bot will attempt to store the last seen ID into the DB. If it fails, this causes the last seen tweet to be stale, and if the bot re-queries Twitter, most subsequent tweets from the stale ID will have already been retweeted.Error seen from logs:
Possible solution: attempt to store the last ID in the iterable first, and if this fails then we should not continue with retweets.
The text was updated successfully, but these errors were encountered: