GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `twits`
--
LOCKTABLES`twits`WRITE;
/*!40000 ALTER TABLE `twits` DISABLE KEYS */;
INSERTINTO`twits`VALUES(1,'i am not a bot',1,'2017-12-23 08:17:07'),(2,'nor me; i am also not a bot',2,'2017-12-23 08:17:38'),(3,'i am a bot that hunts bots - beware!!! editing!',3,'2017-12-23 08:18:37'),(4,'test user id = 1',1,'2018-02-04 16:42:23');
/*!40000 ALTER TABLE `twits` ENABLE KEYS */;
UNLOCKTABLES;
--
-- Table structure for table `users`
--
DROPTABLEIFEXISTS`users`;
/*!40101 SET @saved_cs_client = @@character_set_client */;