├── Django_HaFiz_Sir.rar ├── big.sql ├── big_totaltable.sql ├── excel_manage_20220127.zip └── manage_excel1.sql /Django_HaFiz_Sir.rar: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Supernova1024/35Excel_to_Database/79036d015ccc423c282b73c4e36d4384ed803790/Django_HaFiz_Sir.rar -------------------------------------------------------------------------------- /excel_manage_20220127.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Supernova1024/35Excel_to_Database/79036d015ccc423c282b73c4e36d4384ed803790/excel_manage_20220127.zip -------------------------------------------------------------------------------- /manage_excel1.sql: -------------------------------------------------------------------------------- 1 | -- phpMyAdmin SQL Dump 2 | -- version 5.0.2 3 | -- https://www.phpmyadmin.net/ 4 | -- 5 | -- Host: 127.0.0.1 6 | -- Generation Time: Jan 10, 2022 at 05:09 AM 7 | -- Server version: 10.4.11-MariaDB 8 | -- PHP Version: 7.4.6 9 | 10 | SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; 11 | START TRANSACTION; 12 | SET time_zone = "+00:00"; 13 | 14 | 15 | /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; 16 | /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; 17 | /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; 18 | /*!40101 SET NAMES utf8mb4 */; 19 | 20 | -- 21 | -- Database: `manage_excel1` 22 | -- 23 | 24 | -- -------------------------------------------------------- 25 | 26 | -- 27 | -- Table structure for table `data` 28 | -- 29 | 30 | CREATE TABLE `data` ( 31 | `id` int(12) UNSIGNED NOT NULL, 32 | `phone` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL, 33 | `source` text COLLATE utf8mb4_unicode_ci DEFAULT NULL, 34 | `leadtype` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, 35 | `email` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, 36 | `date` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, 37 | `state` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, 38 | `created_at` timestamp NULL DEFAULT NULL, 39 | `updated_at` timestamp NULL DEFAULT NULL 40 | ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; 41 | 42 | -- 43 | -- Dumping data for table `data` 44 | -- 45 | 46 | INSERT INTO `data` (`id`, `phone`, `source`, `leadtype`, `email`, `date`, `state`, `created_at`, `updated_at`) VALUES 47 | (1, '123', 's123', 'l123', '123@1', '2022-1-8', '2', '2022-01-08 13:45:20', '2022-01-08 13:45:20'), 48 | (2, '5555626358', 'Source A ', 'Student', 'A@aol.com', '01/01/20222', '2', '2022-01-08 13:50:47', '2022-01-08 13:50:47'), 49 | (3, '5.56E+12', 'Source B ', 'Student', 'B@aol.com', '01/01/20222', '2', '2022-01-08 13:50:47', '2022-01-08 13:50:47'), 50 | (4, '4.45E+12', 'Source C ', 'Student', 'C@aol.com', '01/01/20222', '2', '2022-01-08 13:50:47', '2022-01-08 13:50:47'), 51 | (5, '4.50E+11', 'Source C ', 'Student', 'C@aol.com', '', '2', '2022-01-08 13:53:41', '2022-01-08 13:53:41'), 52 | (6, '4.41E+13', 'Source C ', '', 'C@aol.com', '01/01/20222', '2', '2022-01-08 13:53:41', '2022-01-08 13:53:41'), 53 | (7, '1', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/1/2022', '1', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 54 | (8, '2', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/2/2022', '2', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 55 | (9, '3', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/3/2022', '3', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 56 | (10, '4', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/4/2022', '4', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 57 | (11, '5', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/5/2022', '5', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 58 | (12, '6', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/6/2022', '6', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 59 | (13, '7', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/7/2022', '7', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 60 | (14, '8', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/8/2022', '8', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 61 | (15, '9', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/9/2022', '9', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 62 | (16, '10', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/10/2022', '10', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 63 | (17, '11', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/11/2022', '11', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 64 | (18, '12', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/12/2022', '12', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 65 | (19, '13', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/13/2022', '13', '2022-01-08 14:26:47', '2022-01-08 14:26:47'), 66 | (20, '14', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/14/2022', '14', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 67 | (21, '15', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/15/2022', '15', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 68 | (22, '16', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/16/2022', '16', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 69 | (23, '17', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/17/2022', '17', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 70 | (24, '18', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/18/2022', '18', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 71 | (25, '19', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/19/2022', '19', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 72 | (26, '20', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/20/2022', '20', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 73 | (27, '21', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/21/2022', '21', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 74 | (28, '22', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/22/2022', '22', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 75 | (29, '23', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/23/2022', '23', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 76 | (30, '24', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/24/2022', '24', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 77 | (31, '25', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/25/2022', '25', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 78 | (32, '26', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/26/2022', '26', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 79 | (33, '27', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/27/2022', '27', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 80 | (34, '28', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/28/2022', '28', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 81 | (35, '29', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/29/2022', '29', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 82 | (36, '30', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/30/2022', '30', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 83 | (37, '31', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '1/31/2022', '31', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 84 | (38, '32', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/1/2022', '32', '2022-01-08 14:26:48', '2022-01-08 14:26:48'), 85 | (39, '33', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/2/2022', '33', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 86 | (40, '34', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/3/2022', '34', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 87 | (41, '35', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/4/2022', '35', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 88 | (42, '36', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/5/2022', '36', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 89 | (43, '37', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/6/2022', '37', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 90 | (44, '38', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/7/2022', '38', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 91 | (45, '39', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/8/2022', '39', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 92 | (46, '40', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/9/2022', '40', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 93 | (47, '41', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/10/2022', '41', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 94 | (48, '42', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/11/2022', '42', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 95 | (49, '43', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/12/2022', '43', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 96 | (50, '44', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/13/2022', '44', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 97 | (51, '45', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/14/2022', '45', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 98 | (52, '46', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/15/2022', '46', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 99 | (53, '47', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/16/2022', '47', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 100 | (54, '48', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/17/2022', '48', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 101 | (55, '49', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/18/2022', '49', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 102 | (56, '50', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/19/2022', '50', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 103 | (57, '51', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/20/2022', '51', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 104 | (58, '52', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/21/2022', '52', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 105 | (59, '53', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/22/2022', '53', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 106 | (60, '54', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/23/2022', '54', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 107 | (61, '55', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/24/2022', '55', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 108 | (62, '56', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/25/2022', '56', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 109 | (63, '57', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/26/2022', '57', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 110 | (64, '58', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/27/2022', '58', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 111 | (65, '59', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '2/28/2022', '59', '2022-01-08 14:26:49', '2022-01-08 14:26:49'), 112 | (66, '60', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/1/2022', '60', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 113 | (67, '61', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/2/2022', '61', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 114 | (68, '62', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/3/2022', '62', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 115 | (69, '63', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/4/2022', '63', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 116 | (70, '64', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/5/2022', '64', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 117 | (71, '65', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/6/2022', '65', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 118 | (72, '66', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/7/2022', '66', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 119 | (73, '67', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/8/2022', '67', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 120 | (74, '68', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/9/2022', '68', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 121 | (75, '69', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/10/2022', '69', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 122 | (76, '70', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/11/2022', '70', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 123 | (77, '71', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/12/2022', '71', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 124 | (78, '72', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/13/2022', '72', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 125 | (79, '73', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/14/2022', '73', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 126 | (80, '74', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/15/2022', '74', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 127 | (81, '75', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/16/2022', '75', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 128 | (82, '76', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/17/2022', '76', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 129 | (83, '77', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/18/2022', '77', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 130 | (84, '78', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/19/2022', '78', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 131 | (85, '79', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/20/2022', '79', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 132 | (86, '80', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/21/2022', '80', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 133 | (87, '81', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/22/2022', '81', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 134 | (88, '82', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/23/2022', '82', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 135 | (89, '83', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/24/2022', '83', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 136 | (90, '84', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/25/2022', '84', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 137 | (91, '85', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/26/2022', '85', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 138 | (92, '86', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/27/2022', '86', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 139 | (93, '87', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/28/2022', '87', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 140 | (94, '88', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/29/2022', '88', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 141 | (95, '89', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/30/2022', '89', '2022-01-08 14:26:50', '2022-01-08 14:26:50'), 142 | (96, '90', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '3/31/2022', '90', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 143 | (97, '91', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/1/2022', '91', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 144 | (98, '92', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/2/2022', '92', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 145 | (99, '93', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/3/2022', '93', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 146 | (100, '94', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/4/2022', '94', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 147 | (101, '95', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/5/2022', '95', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 148 | (102, '96', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/6/2022', '96', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 149 | (103, '97', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/7/2022', '97', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 150 | (104, '98', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/8/2022', '98', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 151 | (105, '99', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/9/2022', '99', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 152 | (106, '100', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/10/2022', '100', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 153 | (107, '101', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/11/2022', '101', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 154 | (108, '102', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/12/2022', '102', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 155 | (109, '103', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/13/2022', '103', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 156 | (110, '104', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/14/2022', '104', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 157 | (111, '105', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/15/2022', '105', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 158 | (112, '106', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/16/2022', '106', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 159 | (113, '107', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/17/2022', '107', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 160 | (114, '108', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/18/2022', '108', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 161 | (115, '109', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/19/2022', '109', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 162 | (116, '110', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/20/2022', '110', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 163 | (117, '111', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/21/2022', '111', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 164 | (118, '112', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/22/2022', '112', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 165 | (119, '113', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/23/2022', '113', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 166 | (120, '114', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/24/2022', '114', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 167 | (121, '115', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/25/2022', '115', '2022-01-08 14:26:51', '2022-01-08 14:26:51'), 168 | (122, '116', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/26/2022', '116', '2022-01-08 14:26:52', '2022-01-08 14:26:52'), 169 | (123, '117', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/27/2022', '117', '2022-01-08 14:26:52', '2022-01-08 14:26:52'); 170 | INSERT INTO `data` (`id`, `phone`, `source`, `leadtype`, `email`, `date`, `state`, `created_at`, `updated_at`) VALUES 171 | (124, '118', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/28/2022', '118', '2022-01-08 14:26:52', '2022-01-08 14:26:52'), 172 | (125, '119', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/29/2022', '119', '2022-01-08 14:26:52', '2022-01-08 14:26:52'), 173 | (126, '120', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '4/30/2022', '120', '2022-01-08 14:26:52', '2022-01-08 14:26:52'), 174 | (127, '121', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '5/1/2022', '121', '2022-01-08 14:26:52', '2022-01-08 14:26:52'), 175 | (128, '122', 'Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the --force flag:', 'Student', 'A@aol.com', '5/2/2022', '122', '2022-01-08 14:26:52', '2022-01-08 14:26:52'); 176 | 177 | -- -------------------------------------------------------- 178 | 179 | -- 180 | -- Table structure for table `failed_jobs` 181 | -- 182 | 183 | CREATE TABLE `failed_jobs` ( 184 | `id` bigint(20) UNSIGNED NOT NULL, 185 | `uuid` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL, 186 | `connection` text COLLATE utf8mb4_unicode_ci NOT NULL, 187 | `queue` text COLLATE utf8mb4_unicode_ci NOT NULL, 188 | `payload` longtext COLLATE utf8mb4_unicode_ci NOT NULL, 189 | `exception` longtext COLLATE utf8mb4_unicode_ci NOT NULL, 190 | `failed_at` timestamp NOT NULL DEFAULT current_timestamp() 191 | ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; 192 | 193 | -- -------------------------------------------------------- 194 | 195 | -- 196 | -- Table structure for table `migrations` 197 | -- 198 | 199 | CREATE TABLE `migrations` ( 200 | `id` int(10) UNSIGNED NOT NULL, 201 | `migration` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL, 202 | `batch` int(11) NOT NULL 203 | ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; 204 | 205 | -- 206 | -- Dumping data for table `migrations` 207 | -- 208 | 209 | INSERT INTO `migrations` (`id`, `migration`, `batch`) VALUES 210 | (1, '2014_10_12_000000_create_users_table', 1), 211 | (2, '2014_10_12_100000_create_password_resets_table', 1), 212 | (3, '2019_08_19_000000_create_failed_jobs_table', 1), 213 | (4, '2022_01_08_114257_create_data_table', 2); 214 | 215 | -- -------------------------------------------------------- 216 | 217 | -- 218 | -- Table structure for table `password_resets` 219 | -- 220 | 221 | CREATE TABLE `password_resets` ( 222 | `email` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL, 223 | `token` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL, 224 | `created_at` timestamp NULL DEFAULT NULL 225 | ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; 226 | 227 | -- -------------------------------------------------------- 228 | 229 | -- 230 | -- Table structure for table `users` 231 | -- 232 | 233 | CREATE TABLE `users` ( 234 | `id` bigint(20) UNSIGNED NOT NULL, 235 | `name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL, 236 | `email` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL, 237 | `email_verified_at` timestamp NULL DEFAULT NULL, 238 | `password` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL, 239 | `level` int(11) NOT NULL, 240 | `remember_token` varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT NULL, 241 | `created_at` timestamp NULL DEFAULT NULL, 242 | `updated_at` timestamp NULL DEFAULT NULL 243 | ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; 244 | 245 | -- 246 | -- Dumping data for table `users` 247 | -- 248 | 249 | INSERT INTO `users` (`id`, `name`, `email`, `email_verified_at`, `password`, `level`, `remember_token`, `created_at`, `updated_at`) VALUES 250 | (1, 'admin', 'admin@admin.com', NULL, '$2y$10$1A9BSrVIqYS9gMQG0Gcxs.G6MkZDOINqR28.5v7PxVuVOHf1s1Goy', 1, NULL, '2022-01-08 08:09:58', '2022-01-08 08:09:58'), 251 | (2, 'user1', 'user1gmail.com', NULL, '$2y$10$Sm9Rfwb5iAhoPlcTOmgPHuLwOgy2J9VxGd7JCOzOnWlu6gYy.UKja', 1, NULL, '2022-01-08 08:10:34', '2022-01-08 08:10:34'), 252 | (3, 'user21', 'user12@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 253 | (4, 'user22', 'user22@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 254 | (5, 'user32', 'user32@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 255 | (6, 'user42', 'user42@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 256 | (7, 'user52', 'user52@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 257 | (8, 'user62', 'user62@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 258 | (9, 'user72', 'user72@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 259 | (10, 'user92', 'user82@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 260 | (11, 'user112', 'user92@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 261 | (12, 'user122', 'user112@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 262 | (13, 'user213', 'user122@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 263 | (14, 'user214', 'user132@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 264 | (15, 'user215', 'user142@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 265 | (16, 'user216', 'user152@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 266 | (17, 'user217', 'user162@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 267 | (18, 'user218', 'user172@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 268 | (19, 'user219', 'user182@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 269 | (20, 'user220', 'user192@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'), 270 | (21, 'user221', 'user222@gmail.com', NULL, '$2y$10$821x7/8Kv8cYQkvHdE9HMOQt2Ue5NgCikKSGUKHC5OEQ6Gr0ua0fm', 2, NULL, '2022-01-08 08:11:00', '2022-01-08 08:11:00'); 271 | 272 | -- 273 | -- Indexes for dumped tables 274 | -- 275 | 276 | -- 277 | -- Indexes for table `data` 278 | -- 279 | ALTER TABLE `data` 280 | ADD PRIMARY KEY (`id`), 281 | ADD UNIQUE KEY `data_phone_unique` (`phone`); 282 | 283 | -- 284 | -- Indexes for table `failed_jobs` 285 | -- 286 | ALTER TABLE `failed_jobs` 287 | ADD PRIMARY KEY (`id`), 288 | ADD UNIQUE KEY `failed_jobs_uuid_unique` (`uuid`); 289 | 290 | -- 291 | -- Indexes for table `migrations` 292 | -- 293 | ALTER TABLE `migrations` 294 | ADD PRIMARY KEY (`id`); 295 | 296 | -- 297 | -- Indexes for table `password_resets` 298 | -- 299 | ALTER TABLE `password_resets` 300 | ADD KEY `password_resets_email_index` (`email`); 301 | 302 | -- 303 | -- Indexes for table `users` 304 | -- 305 | ALTER TABLE `users` 306 | ADD PRIMARY KEY (`id`), 307 | ADD UNIQUE KEY `users_email_unique` (`email`); 308 | 309 | -- 310 | -- AUTO_INCREMENT for dumped tables 311 | -- 312 | 313 | -- 314 | -- AUTO_INCREMENT for table `data` 315 | -- 316 | ALTER TABLE `data` 317 | MODIFY `id` int(12) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=132; 318 | 319 | -- 320 | -- AUTO_INCREMENT for table `failed_jobs` 321 | -- 322 | ALTER TABLE `failed_jobs` 323 | MODIFY `id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; 324 | 325 | -- 326 | -- AUTO_INCREMENT for table `migrations` 327 | -- 328 | ALTER TABLE `migrations` 329 | MODIFY `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5; 330 | 331 | -- 332 | -- AUTO_INCREMENT for table `users` 333 | -- 334 | ALTER TABLE `users` 335 | MODIFY `id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=22; 336 | COMMIT; 337 | 338 | /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; 339 | /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; 340 | /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; 341 | --------------------------------------------------------------------------------