There is a switch in database_commands.insertTweet, skipDupcliates that when set to True (default) it will insert any tweet that it finds. However, if it is set to False it should be able to check first if that tweet exists and then it should have insertTweet return False so that it can stop there.
This functionality is important if you want to get new tweets from a user...that is it will automatically stop when it finds it already has tweets. Since tweets are in chronological order, the place it stops will be the place it started last time.
There is a switch in
database_commands.insertTweet,skipDupcliatesthat when set toTrue(default) it will insert any tweet that it finds. However, if it is set toFalseit should be able to check first if that tweet exists and then it should haveinsertTweetreturnFalseso that it can stop there.This functionality is important if you want to get new tweets from a user...that is it will automatically stop when it finds it already has tweets. Since tweets are in chronological order, the place it stops will be the place it started last time.