1 row sorted by full_text descending

View and edit SQL

Suggested facets: updated_at (date)

id created_at updated_at deleted_at author_id retweeted source display_text_from_idx display_text_to_idx favorite_count truncated retweet_count possibly_sensitive created favorited full_text ▲ lang in_reply_to_user_id in_reply_to_status_id
1344339046735224836 2021-02-22 22:06:09.208388+03:00 2021-02-22 22:06:09.208388+03:00     0 <a href="http://twitter.com/download/iphone" rel="nofollow">Twitter for iPhone</a> 0 49 1 0 0 0 2020-12-30 17:46:20+00:00 0 Superhuman, but for tiktoks your friends send you en    

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE `twitter_tweets` (`id` integer,`created_at` datetime,`updated_at` datetime,`deleted_at` datetime,`author_id` integer,`retweeted` numeric,`source` text,`display_text_from_idx` integer,`display_text_to_idx` integer,`favorite_count` integer,`truncated` numeric,`retweet_count` integer,`possibly_sensitive` numeric,`created` datetime,`favorited` numeric,`full_text` text,`lang` text,`in_reply_to_user_id` integer,`in_reply_to_status_id` integer,PRIMARY KEY (`id`),CONSTRAINT `fk_twitter_tweets_author` FOREIGN KEY (`author_id`) REFERENCES `twitter_users`(`id`),CONSTRAINT `fk_twitter_tweets_in_reply_to_user` FOREIGN KEY (`in_reply_to_user_id`) REFERENCES `twitter_users`(`id`),CONSTRAINT `fk_twitter_tweets_in_reply_to_status` FOREIGN KEY (`in_reply_to_status_id`) REFERENCES `twitter_tweets`(`id`));
CREATE INDEX `idx_twitter_tweets_deleted_at` ON `twitter_tweets`(`deleted_at`);