R5.10 kompatibel machen #33
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Passt für mich, Danke! 🙌 |
bloep
commented
Mar 18, 2020
Comment on lines
+667
to
+700
| DROP TABLE IF EXISTS `rex_user`; | ||
| CREATE TABLE `rex_user` ( | ||
| `id` int(10) unsigned NOT NULL AUTO_INCREMENT, | ||
| `name` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, | ||
| `description` text COLLATE utf8_unicode_ci, | ||
| `login` varchar(50) COLLATE utf8_unicode_ci NOT NULL, | ||
| `password` varchar(255) COLLATE utf8_unicode_ci NOT NULL, | ||
| `email` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, | ||
| `status` tinyint(1) NOT NULL, | ||
| `admin` tinyint(1) NOT NULL, | ||
| `language` varchar(255) COLLATE utf8_unicode_ci NOT NULL, | ||
| `startpage` varchar(255) COLLATE utf8_unicode_ci NOT NULL, | ||
| `role` text COLLATE utf8_unicode_ci, | ||
| `login_tries` tinyint(4) DEFAULT NULL, | ||
| `createdate` datetime NOT NULL, | ||
| `lasttrydate` datetime NOT NULL, | ||
| `lastlogin` datetime DEFAULT NULL, | ||
| `session_id` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, | ||
| `cookiekey` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, | ||
| `revision` int(10) unsigned NOT NULL, | ||
| `createuser` varchar(255) COLLATE utf8_unicode_ci NOT NULL, | ||
| `updatedate` datetime NOT NULL, | ||
| `updateuser` varchar(255) COLLATE utf8_unicode_ci NOT NULL, | ||
| PRIMARY KEY (`id`), | ||
| UNIQUE KEY `login` (`login`) | ||
| ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; | ||
|
|
||
| LOCK TABLES `rex_user` WRITE; | ||
| /*!40000 ALTER TABLE `rex_user` DISABLE KEYS */; | ||
| INSERT INTO `rex_user` VALUES | ||
| (1,'Administrator',NULL,'admin','$2y$10$xMbThw7FOeRoqKsQ7cT4Mu5kYj7oCyJ6./lCPMEOGhq39E//CcFvu',NULL,1,1,'','',NULL,0,'2020-03-08 15:27:05','2020-03-15 15:52:23','2020-03-15 15:52:23','ftufnn5agtkvlcvmugribv4is2',NULL,0,'setup','0000-00-00 00:00:00',''); | ||
| /*!40000 ALTER TABLE `rex_user` ENABLE KEYS */; | ||
| UNLOCK TABLES; | ||
|
|
There was a problem hiding this comment.
@schuer mist, das ist hier mit reingerutscht....
There was a problem hiding this comment.
Kein Ding. Soll ich mal ein neues Release erstellen, oder bist du dran? @bloep
There was a problem hiding this comment.
ich bin da net dran, wenn es im release fertig ist, könnte man danach direkt das docker-image fertig haben. den rest habe ich soweit am stehen.
wenn du ein korrigiertes release machen könntest wäre super 😘
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ich habe ein update auf R5.10 gemacht und einen neuen export erstellt.