API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Oct 25th, 2018
451
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
MySQL 40.17 KB | None | 0 0
raw download clone embed print report
  1. -- phpMyAdmin SQL Dump
  2. -- version 4.7.3
  3. -- https://www.phpmyadmin.net/
  4. --
  5. -- Host: localhost:3306
  6. -- Generation Time: Oct 26, 2018 at 12:45 AM
  7. -- Server version: 5.6.35
  8. -- PHP Version: 7.1.1
  9.  
  10. SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
  11. SET time_zone = "+00:00";
  12.  
  13. --
  14. -- Database: `soccercric_db`
  15. --
  16.  
  17. -- --------------------------------------------------------
  18.  
  19. --
  20. -- Table structure for table `admin`
  21. --
  22.  
  23. CREATE TABLE `admin` (
  24.   `id` int(11) NOT NULL,
  25.   `admin_name` varchar(20) COLLATE utf16_unicode_ci NOT NULL,
  26.   `username` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  27.   `password` varchar(50) COLLATE utf16_unicode_ci NOT NULL,
  28.   `role` varchar(20) COLLATE utf16_unicode_ci NOT NULL
  29. ) ENGINE=InnoDB DEFAULT CHARSET=utf16 COLLATE=utf16_unicode_ci;
  30.  
  31. --
  32. -- Dumping data for table `admin`
  33. --
  34.  
  35. INSERT INTO `admin` (`id`, `admin_name`, `username`, `password`, `role`) VALUES
  36. (4, 'Tanyer Ahmed', 'tanyer', 'e10adc3949ba59abbe56e057f20f883e', 'admin');
  37.  
  38. -- --------------------------------------------------------
  39.  
  40. --
  41. -- Table structure for table `child_info`
  42. --
  43.  
  44. CREATE TABLE `child_info` (
  45.   `child_id` int(11) NOT NULL,
  46.   `child_first_name` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  47.   `child_last_name` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  48.   `gender` varchar(10) COLLATE utf16_unicode_ci NOT NULL,
  49.   `dob` date NOT NULL,
  50.   `class_coordinator` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  51.   `school` varchar(40) COLLATE utf16_unicode_ci NOT NULL,
  52.   `relation` varchar(15) COLLATE utf16_unicode_ci NOT NULL,
  53.   `sports_type` varchar(10) COLLATE utf16_unicode_ci NOT NULL,
  54.   `medical_condition` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  55.   `parent_id` int(11) NOT NULL
  56. ) ENGINE=InnoDB DEFAULT CHARSET=utf16 COLLATE=utf16_unicode_ci;
  57.  
  58. --
  59. -- Dumping data for table `child_info`
  60. --
  61.  
  62. INSERT INTO `child_info` (`child_id`, `child_first_name`, `child_last_name`, `gender`, `dob`, `class_coordinator`, `school`, `relation`, `sports_type`, `medical_condition`, `parent_id`) VALUES
  63. (1, 'abcd', 'efgh', '', '0000-00-00', 'None', 'Blue Bird', 'Uncle', 'soccer', 'None', 1),
  64. (2, 'pqrs', 'uvwx', '', '0000-00-00', 'None', 'Blue Bird', 'uncle', 'cricket', 'None', 1),
  65. (3, 'b', 'b', 'male', '0000-00-00', 'b', 'b', 'b', 'soccer', 'b', 2),
  66. (4, 'c', 'c', 'female', '0000-00-00', 'c', 'c', 'c', 'cricket', 'c', 2),
  67. (5, 'd', 'd', 'male', '0000-00-00', 'd', 'd', 'd', 'soccer', 'd', 2),
  68. (6, 'Akram', 'Haque', 'male', '2013-11-05', 'None', 'Blue Bird', 'Father', 'soccer', 'Good', 3),
  69. (7, 'Foyex', 'Haque', 'male', '2016-07-06', 'None', 'Blue Bird', 'Father', 'soccer', 'Good', 3),
  70. (8, 'asd', 'h', 'male', '2017-05-25', 'ads', 'asd', 'asda', 'soccer', 'asds', 4),
  71. (9, 'b', 'bb', 'male', '2017-05-25', 'b', 'bb', 'b', 'soccer', 'b', 5),
  72. (10, 'n', 'nn', 'male', '2017-05-23', 'n', 'n', 'n', 'soccer', 'n', 6),
  73. (11, 'n', 'n', 'male', '2017-05-17', 'n', 'n', 'n', 'soccer', 'sa', 7),
  74. (12, 'b', 'b', 'male', '0000-00-00', 'b', 'b', 'b', 'soccer', 'b', 8),
  75. (13, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 9),
  76. (14, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 10),
  77. (15, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 11),
  78. (16, 'b', 'b', 'male', '0000-00-00', 'b', 'b', 'b', 'soccer', 'b', 12),
  79. (17, 'nn', 'nn', 'male', '0000-00-00', 'nnn', 'nnn', 'nnn', 'soccer', 'nn', 13),
  80. (18, 'j', 'j', 'male', '0000-00-00', 'j', 'j', 'j', 'soccer', 'j', 14),
  81. (19, 'u', 'u', 'male', '0000-00-00', 'u', 'u', 'u', 'soccer', 'u', 15),
  82. (20, 'j', 'j', 'male', '0000-00-00', 'j', 'j', 'j', 'soccer', 'l', 16),
  83. (21, 'u', 'u', 'male', '0000-00-00', 'u', 'u', 'u', 'soccer', 'u', 17),
  84. (22, 'p', 'p', 'male', '0000-00-00', 'p', 'p', 'p', 'soccer', 'p', 18),
  85. (23, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 19),
  86. (24, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 20),
  87. (25, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 21),
  88. (26, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 22),
  89. (27, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 23),
  90. (28, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 24),
  91. (29, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 25),
  92. (30, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 26),
  93. (31, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 27),
  94. (32, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 28),
  95. (33, 'n', 'nn', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 29),
  96. (34, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 30),
  97. (35, 'm', 'm', 'male', '0000-00-00', 'm', 'm', 'm', 'soccer', 'm', 31),
  98. (36, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 32),
  99. (37, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 33),
  100. (38, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 35),
  101. (39, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 36),
  102. (40, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 37),
  103. (41, 'n', 'n', 'male', '0000-00-00', 'n', 'n', 'n', 'soccer', 'n', 38),
  104. (42, 'a', 'a', 'male', '0000-00-00', 'a', 'a', 'a', 'soccer', 'a', 39),
  105. (43, 'Rahat', 'Khan', 'male', '0000-00-00', 'Tanyer AHmed', 'Blue Bird School and College', 'Father', 'soccer', 'No medical condition', 40),
  106. (44, 'k', 'k', 'male', '0000-00-00', 'k', 'k', 'k', 'soccer', 'k', 41),
  107. (45, 'k', 'k', 'male', '0000-00-00', 'k', 'k', 'k', 'soccer', 'k', 42),
  108. (46, 'k', 'k', 'male', '0000-00-00', 'k', 'k', 'k', 'soccer', 'k', 43),
  109. (47, 'k', 'k', 'male', '0000-00-00', 'k', 'k', 'k', 'soccer', 'k', 44),
  110. (48, 'k', 'k', 'male', '0000-00-00', 'k', 'k', 'k', 'soccer', 'k', 45),
  111. (49, 'k', 'k', 'male', '0000-00-00', 'k', 'k', 'k', 'soccer', 'k', 46),
  112. (50, 'k', 'k', 'male', '0000-00-00', 'k', 'k', 'k', 'soccer', 'k', 47),
  113. (51, 'k', 'k', 'male', '0000-00-00', 'k', 'k', 'k', 'soccer', 'k', 48);
  114.  
  115. -- --------------------------------------------------------
  116.  
  117. --
  118. -- Table structure for table `classes`
  119. --
  120.  
  121. CREATE TABLE `classes` (
  122.   `class_id` int(11) NOT NULL,
  123.   `coach_name` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  124.   `age` varchar(10) COLLATE utf16_unicode_ci NOT NULL,
  125.   `location` varchar(40) COLLATE utf16_unicode_ci NOT NULL,
  126.   `area` varchar(40) COLLATE utf16_unicode_ci NOT NULL,
  127.   `quantity` int(10) NOT NULL,
  128.   `seasson` varchar(20) COLLATE utf16_unicode_ci NOT NULL,
  129.   `day` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  130.   `start_date` date NOT NULL,
  131.   `end_date` date NOT NULL,
  132.   `start_time` varchar(40) COLLATE utf16_unicode_ci NOT NULL,
  133.   `end_time` varchar(40) COLLATE utf16_unicode_ci NOT NULL,
  134.   `price` float NOT NULL,
  135.   `registered` int(1) NOT NULL,
  136.   `name` varchar(40) COLLATE utf16_unicode_ci NOT NULL,
  137.   `lat` double NOT NULL,
  138.   `lang` double NOT NULL,
  139.   `class_details` varchar(1000) COLLATE utf16_unicode_ci NOT NULL
  140. ) ENGINE=InnoDB DEFAULT CHARSET=utf16 COLLATE=utf16_unicode_ci;
  141.  
  142. --
  143. -- Dumping data for table `classes`
  144. --
  145.  
  146. INSERT INTO `classes` (`class_id`, `coach_name`, `age`, `location`, `area`, `quantity`, `seasson`, `day`, `start_date`, `end_date`, `start_time`, `end_time`, `price`, `registered`, `name`, `lat`, `lang`, `class_details`) VALUES
  147. (14, 'Tanyer Ahmed', '', 'MANHATTAN', 'ASTORIA PARK', 5, 'FALL', 'SATURDAY', '2017-06-21', '2017-06-21', '12:00', '03:00', 0, 0, 'Ramdan Special', 40.7796684, -73.9215888, ''),
  148. (15, 'Tanyer', '3', 'QUEENS', 'ASTORIA PARK', 0, 'SUMMER', 'FRIDAY', '2017-05-28', '2017-05-28', '12:00:00pm', '04:30:00pm', 0, 0, 'Ramadan ', 0, 0, ''),
  149. (16, 'Nadim', '6-7', 'QUEENS', 'ASTORIA PARK', 14, 'SUMMER', 'SATURDAY', '2017-06-21', '2017-06-21', '12:00:00pm', '05:00:00pm', 180, 0, 'Fun class', 0, 0, ''),
  150. (17, 'Nadim', '2-3', 'BROOKLYN', 'ASTORIA PARK', 6, 'SPRING', 'SUNDAY', '0000-00-00', '0000-00-00', '12:00', '12:00', 180, 0, 'Toddler Class', 0, 0, ''),
  151. (18, 'Nadim', '2-3', 'BROOKLYN', 'ASTORIA PARK', 10, 'SPRING', 'SUNDAY', '0000-00-00', '0000-00-00', '12:00', '12:00', 180, 0, 'Toddler Class', 0, 0, ''),
  152. (19, 'Nadim', '4-5', 'BROOKLYN', 'ASTORIA PARK', 10, 'FALL', 'SATURDAY', '2017-06-25', '2017-06-29', '12:00', '05:00', 180, 0, 'Toddler Class', 0, 0, ''),
  153. (20, 'nadim', '2-3', 'BROOKLYN', 'ASTORIA PARK', 10, 'FALL', 'SATURDAY', '2017-06-26', '2017-06-28', '12:00', '05:00', 0, 0, 'Toddler Class', 0, 0, ''),
  154. (21, 'Nadim', '2-3', 'MANHATTAN', 'Astoria park', 3, 'FALL', 'SUNDAY', '2017-07-14', '2017-07-14', '12:00', '05:35', 190, 0, 'Toddler Class', 40.7796684, -73.9215888, 'This is test'),
  155. (22, 'Nadim', '2-3', 'MANHATTAN', 'Fsafsaffsf', 12, 'FALL', 'THURSDAY', '2018-02-09', '2018-02-17', '12:00', '03:00', 120, 0, 'Practice class', 312123, 132123312, 'asddaadsdas');
  156.  
  157. -- --------------------------------------------------------
  158.  
  159. --
  160. -- Table structure for table `class_request`
  161. --
  162.  
  163. CREATE TABLE `class_request` (
  164.   `request_id` int(11) NOT NULL,
  165.   `fullname` varchar(50) NOT NULL,
  166.   `location` varchar(30) NOT NULL,
  167.   `email` varchar(50) NOT NULL,
  168.   `message` varchar(1000) NOT NULL
  169. ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
  170.  
  171. --
  172. -- Dumping data for table `class_request`
  173. --
  174.  
  175. INSERT INTO `class_request` (`request_id`, `fullname`, `location`, `email`, `message`) VALUES
  176. (1, 'nadim', 'Manhattan', 'na146363@gmail.com', 'This is a test message'),
  177. (2, 'nadim', 'Manhattan', 'na146363@gmail.com', 'This is a test message'),
  178. (3, 'nadim', 'Manhattan', 'na146363@gmail.com', 'This is a test message'),
  179. (4, 'nadim', 'Manhattan', 'na146363@gmail.com', 'This is a test message'),
  180. (5, 'nadim', 'Manhattan', 'na146363@gmail.com', 'This is a test message'),
  181. (6, 'nadim', 'Manhattan', 'na146363@gmail.com', 'This is a test message'),
  182. (7, 'nadim', 'Manhattan', 'na146363@gmail.com', 'ths asmkldak nasfk ask kla a '),
  183. (8, 'nadim', 'Manhattan', 'na146363@gmail.com', 'ada sda'),
  184. (9, 'asdasd', 'sadansjkdna', 'sdasdasdad', 'sadasdasdas'),
  185. (10, 'nadim', 'Manhattan', 'na146363@gmail.com', 'sadasdasdasda'),
  186. (11, 'nadim', 'Manhattan', 'na146363@gmail.com', 'sadasdasdasda'),
  187. (12, 'nadim', 'Manhattan', 'na146363@gmail.com', 'adkjasdnadklakldkla'),
  188. (13, 'nadim', 'Manhattan', 'na146363@gmail.com', 'adkjasdnadklakldkla'),
  189. (14, 'nadim', 'Manhattan', 'na146363@gmail.com', 'adkjasdnadklakldkla'),
  190. (15, 'nadim', 'Manhattan', 'na146363@gmail.com', 'adkjasdnadklakldkla'),
  191. (16, 'nadim', 'Manhattan', 'na146363@gmail.com', 'adkjasdnadklakldkla'),
  192. (17, 'asdas', 'k', 'k', 'kk'),
  193. (18, 'asdas', 'k', 'k', 'kk'),
  194. (19, 'nadim', 'Manhattan', 'na146363@gmail.com', 'asdasdad'),
  195. (20, 'nadim', 'Manhattan', 'na146363@gmail.com', 'asdasdasd\r\n'),
  196. (21, 'nM', 'Manhattan', 'na146363@gmail.com', 'ddddd');
  197.  
  198. -- --------------------------------------------------------
  199.  
  200. --
  201. -- Table structure for table `coach`
  202. --
  203.  
  204. CREATE TABLE `coach` (
  205.   `id` int(11) NOT NULL,
  206.   `coach_name` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  207.   `location` varchar(40) COLLATE utf16_unicode_ci NOT NULL,
  208.   `bio` varchar(2000) COLLATE utf16_unicode_ci NOT NULL,
  209.   `profile_image` varchar(100) COLLATE utf16_unicode_ci NOT NULL
  210. ) ENGINE=InnoDB DEFAULT CHARSET=utf16 COLLATE=utf16_unicode_ci;
  211.  
  212. --
  213. -- Dumping data for table `coach`
  214. --
  215.  
  216. INSERT INTO `coach` (`id`, `coach_name`, `location`, `bio`, `profile_image`) VALUES
  217. (1, 'Nadim haque Khana sda d', 'UK', 'madmad m,a,.md ,.aThis is a test', 'uploads/news/images/17716292015952e05843bc7.pngJPG'),
  218. (2, 'Nadim haque', 'Sylhet', 'Nadim haque is a good footballer\r\nhe can dribble in any weather ', 'uploads/coach/images/10661721155955283ed9b0d.png'),
  219. (3, 'Nadim haque', 'Sylhet', 'Nadim haque is a good footballer\r\nhe can dribble in any weather ', 'uploads/coach/images/6810825045955295be6761.png'),
  220. (4, 'jjjjjjjjjjj j j ', 'jj', 'j\r\nj\r\nj\r\n\r\nj\r\nj\r\nj\r\n\r\nj\r\nj', 'uploads/coach/images/12906611795955296a470c0.'),
  221. (5, 'anannanan', 'nansa', 'lll l l l ll\r\nk\r\nk\r\nk\r\nk\r\nk\r\n', 'uploads/coach/images/1723374176595529884c431.png');
  222.  
  223. -- --------------------------------------------------------
  224.  
  225. --
  226. -- Table structure for table `contact_page`
  227. --
  228.  
  229. CREATE TABLE `contact_page` (
  230.   `id` int(11) NOT NULL,
  231.   `message` varchar(500) COLLATE utf16_unicode_ci NOT NULL,
  232.   `name` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  233.   `phone` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  234.   `email` varchar(40) COLLATE utf16_unicode_ci NOT NULL,
  235.   `time` varchar(40) COLLATE utf16_unicode_ci NOT NULL
  236. ) ENGINE=InnoDB DEFAULT CHARSET=utf16 COLLATE=utf16_unicode_ci;
  237.  
  238. --
  239. -- Dumping data for table `contact_page`
  240. --
  241.  
  242. INSERT INTO `contact_page` (`id`, `message`, `name`, `phone`, `email`, `time`) VALUES
  243. (1, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  244. (2, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  245. (3, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  246. (4, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  247. (5, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  248. (6, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  249. (7, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  250. (8, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  251. (9, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  252. (10, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  253. (11, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  254. (12, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  255. (13, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  256. (14, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  257. (15, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  258. (16, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  259. (17, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  260. (18, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  261. (19, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  262. (20, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  263. (21, 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop p', 'Mahmudul Haque Nadim', '01731001333', 'na146363@gmail.com', '2017-05-10 22:59:58'),
  264. (22, 'Hello', 'Soccercric', '123123123', 'soccercricny@gmail.com', '2017-05-24 13:59:54'),
  265. (23, 'Hello', 'Shan', '123123123', 'khanshan690@gmail.com', '2017-05-24 14:02:02'),
  266. (24, 'Hello', 'Rana', '123123123', 'tuhelrana@gmail.com', '2017-05-24 14:10:06');
  267.  
  268. -- --------------------------------------------------------
  269.  
  270. --
  271. -- Table structure for table `customers`
  272. --
  273.  
  274. CREATE TABLE `customers` (
  275.   `customerid` int(11) NOT NULL,
  276.   `customer_name` varchar(20) NOT NULL,
  277.   `child_first_name` varchar(30) NOT NULL,
  278.   `email` varchar(80) NOT NULL,
  279.   `address` varchar(80) NOT NULL,
  280.   `phone` varchar(20) NOT NULL
  281. ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
  282.  
  283. --
  284. -- Dumping data for table `customers`
  285. --
  286.  
  287. INSERT INTO `customers` (`customerid`, `customer_name`, `child_first_name`, `email`, `address`, `phone`) VALUES
  288. (1, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  289. (2, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  290. (3, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  291. (4, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  292. (5, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  293. (6, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  294. (7, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  295. (8, 'k k', 'k', 'na146363@gmail.com', 'k', 'k'),
  296. (9, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  297. (10, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  298. (11, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  299. (12, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  300. (13, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  301. (14, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  302. (15, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  303. (16, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  304. (17, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  305. (18, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  306. (19, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  307. (20, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  308. (21, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n'),
  309. (22, 'n n', 'a', 'nadimcse.official@gmail.com', 'n', 'n');
  310.  
  311. -- --------------------------------------------------------
  312.  
  313. --
  314. -- Table structure for table `gallery`
  315. --
  316.  
  317. CREATE TABLE `gallery` (
  318.   `image_id` int(11) NOT NULL,
  319.   `image_title` varchar(100) COLLATE utf16_unicode_ci NOT NULL,
  320.   `category` varchar(20) COLLATE utf16_unicode_ci NOT NULL,
  321.   `image` varchar(300) COLLATE utf16_unicode_ci NOT NULL
  322. ) ENGINE=InnoDB DEFAULT CHARSET=utf16 COLLATE=utf16_unicode_ci;
  323.  
  324. --
  325. -- Dumping data for table `gallery`
  326. --
  327.  
  328. INSERT INTO `gallery` (`image_id`, `image_title`, `category`, `image`) VALUES
  329. (1, 'Game of thrones ', 'cricket', 'uploads/gallery/25563591f5313097b2.jpg'),
  330. (3, 'The Library', 'cricket', 'uploads/gallery/1683059202e8fdb82f.jpg'),
  331. (4, 'The Library', 'cricket', 'uploads/gallery/1683059202e8fdb82f.jpg'),
  332. (5, 'The Library', 'cricket', 'uploads/gallery/1683059202e8fdb82f.jpg'),
  333. (6, 'The Library', 'cricket', 'uploads/gallery/1683059202e8fdb82f.jpg'),
  334. (7, 'The Library', 'cricket', 'uploads/gallery/1683059202e8fdb82f.jpg'),
  335. (8, 'The Library', 'cricket', 'uploads/gallery/1683059202e8fdb82f.jpg'),
  336. (9, 'The Library', 'cricket', 'uploads/gallery/1683059202e8fdb82f.jpg'),
  337. (10, 'Game of thrones ', 'cricket', 'uploads/gallery/25563591f5313097b2.jpg'),
  338. (11, 'Game of thrones ', 'cricket', 'uploads/gallery/25563591f5313097b2.jpg'),
  339. (12, 'Game of thrones ', 'cricket', 'uploads/gallery/25563591f5313097b2.jpg'),
  340. (13, 'The Library', 'cricket', 'uploads/gallery/1683059202e8fdb82f.jpg'),
  341. (14, 'The Library', 'cricket', 'uploads/gallery/1683059202e8fdb82f.jpg'),
  342. (15, 'The Library', 'cricket', 'uploads/gallery/1683059202e8fdb82f.jpg'),
  343. (17, 'New Book', 'soccer', 'uploads/gallery/1331759204bc8c675b.jpg'),
  344. (18, 'Nadim', 'cricket', 'uploads/gallery/1718585867595151b256d90.JPG'),
  345. (19, 'Starting ', 'soccer', 'uploads/gallery/147932295759515313828e1.JPG');
  346.  
  347. -- --------------------------------------------------------
  348.  
  349. --
  350. -- Table structure for table `news`
  351. --
  352.  
  353. CREATE TABLE `news` (
  354.   `news_id` int(11) NOT NULL,
  355.   `news_heading` varchar(50) COLLATE utf16_unicode_ci NOT NULL,
  356.   `news_details` varchar(1000) COLLATE utf16_unicode_ci NOT NULL,
  357.   `news_image` varchar(200) COLLATE utf16_unicode_ci NOT NULL,
  358.   `catagory` varchar(20) COLLATE utf16_unicode_ci NOT NULL,
  359.   `admin` varchar(30) COLLATE utf16_unicode_ci NOT NULL
  360. ) ENGINE=InnoDB DEFAULT CHARSET=utf16 COLLATE=utf16_unicode_ci;
  361.  
  362. -- --------------------------------------------------------
  363.  
  364. --
  365. -- Table structure for table `orders`
  366. --
  367.  
  368. CREATE TABLE `orders` (
  369.   `serial` int(11) NOT NULL,
  370.   `date` date NOT NULL,
  371.   `customerid` int(11) NOT NULL
  372. ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
  373.  
  374. --
  375. -- Dumping data for table `orders`
  376. --
  377.  
  378. INSERT INTO `orders` (`serial`, `date`, `customerid`) VALUES
  379. (1, '2017-05-23', 1),
  380. (2, '2017-05-23', 2),
  381. (3, '2017-05-24', 3),
  382. (4, '2017-05-24', 4),
  383. (5, '2017-05-24', 5),
  384. (6, '2017-05-24', 6),
  385. (7, '2017-05-24', 7),
  386. (8, '2017-05-28', 8),
  387. (9, '2017-05-29', 9),
  388. (10, '2018-02-06', 10),
  389. (11, '2018-02-06', 11),
  390. (12, '2018-02-09', 12),
  391. (13, '2018-02-09', 13),
  392. (14, '2018-02-09', 14),
  393. (15, '2018-02-09', 15),
  394. (16, '2018-02-09', 16),
  395. (17, '2018-02-09', 17),
  396. (18, '2018-02-09', 18),
  397. (19, '2018-02-09', 19),
  398. (20, '2018-02-09', 20),
  399. (21, '2018-02-09', 21),
  400. (22, '2018-02-09', 22);
  401.  
  402. -- --------------------------------------------------------
  403.  
  404. --
  405. -- Table structure for table `order_detail`
  406. --
  407.  
  408. CREATE TABLE `order_detail` (
  409.   `orderid` int(11) NOT NULL,
  410.   `customerid` int(11) NOT NULL,
  411.   `productid` int(11) NOT NULL,
  412.   `name` varchar(40) NOT NULL,
  413.   `class_id` int(100) NOT NULL,
  414.   `qty` int(11) NOT NULL,
  415.   `price` float NOT NULL,
  416.   `email` varchar(40) NOT NULL,
  417.   `invoice_no` varchar(255) NOT NULL
  418. ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
  419.  
  420. --
  421. -- Dumping data for table `order_detail`
  422. --
  423.  
  424. INSERT INTO `order_detail` (`orderid`, `customerid`, `productid`, `name`, `class_id`, `qty`, `price`, `email`, `invoice_no`) VALUES
  425. (1, 1, 12, 'Soccer Steps', 0, 1, 1, 'nadimcse.official@gmail.com', ''),
  426. (2, 2, 12, 'Soccer Steps', 0, 1, 1, 'nadimcse.official@gmail.com', ''),
  427. (3, 3, 11, 'Class for olds', 0, 10, 1, 'nadimcse.official@gmail.com', ''),
  428. (4, 4, 11, 'Class for olds', 0, 11, 1, 'nadimcse.official@gmail.com', ''),
  429. (5, 5, 11, 'Class for olds', 11, 11, 1, 'nadimcse.official@gmail.com', ''),
  430. (6, 6, 11, 'Class for olds', 11, 11, 1, 'nadimcse.official@gmail.com', ''),
  431. (7, 7, 11, 'Class for olds', 11, 1, 1, 'nadimcse.official@gmail.com', ''),
  432. (8, 8, 14, 'Ramdan Special', 14, 2, 0, 'na146363@gmail.com', ''),
  433. (9, 9, 6, 'Toddler Group', 0, 1, 10, 'nadimcse.official@gmail.com', ''),
  434. (10, 10, 14, 'Ramdan Special', 14, 1, 0, 'nadimcse.official@gmail.com', ''),
  435. (11, 11, 19, 'Toddler Class', 19, 1, 180, 'nadimcse.official@gmail.com', ''),
  436. (12, 12, 19, 'Toddler Class', 0, 1, 180, 'nadimcse.official@gmail.com', ''),
  437. (13, 13, 22, 'Practice class', 0, 1, 120, 'nadimcse.official@gmail.com', ''),
  438. (14, 14, 17, 'Toddler Class', 17, 2, 180, 'nadimcse.official@gmail.com', ''),
  439. (15, 15, 17, 'Toddler Class', 17, 2, 180, 'nadimcse.official@gmail.com', ''),
  440. (16, 16, 17, 'Toddler Class', 17, 2, 180, 'nadimcse.official@gmail.com', ''),
  441. (17, 17, 17, 'Toddler Class', 17, 3, 180, 'nadimcse.official@gmail.com', ''),
  442. (19, 19, 17, 'Toddler Class', 0, 3, 180, 'nadimcse.official@gmail.com', '63294555'),
  443. (20, 20, 16, 'Fun class', 16, 1, 180, 'nadimcse.official@gmail.com', '43875856'),
  444. (21, 21, 17, 'Toddler Class', 0, 1, 180, 'nadimcse.official@gmail.com', '00929109'),
  445. (22, 22, 17, 'Toddler Class', 17, 1, 180, 'nadimcse.official@gmail.com', '54964863');
  446.  
  447. -- --------------------------------------------------------
  448.  
  449. --
  450. -- Table structure for table `parent_info`
  451. --
  452.  
  453. CREATE TABLE `parent_info` (
  454.   `parent_id` int(11) NOT NULL,
  455.   `first_name` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  456.   `last_name` varchar(20) COLLATE utf16_unicode_ci NOT NULL,
  457.   `username` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  458.   `address` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  459.   `postal_code` varchar(15) COLLATE utf16_unicode_ci NOT NULL,
  460.   `city` varchar(15) COLLATE utf16_unicode_ci NOT NULL,
  461.   `state` varchar(15) COLLATE utf16_unicode_ci NOT NULL,
  462.   `home_phone` varchar(20) COLLATE utf16_unicode_ci NOT NULL,
  463.   `phone` varchar(20) COLLATE utf16_unicode_ci NOT NULL,
  464.   `emergency_contact_name` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  465.   `emergency_contact_number` varchar(20) COLLATE utf16_unicode_ci NOT NULL,
  466.   `email` varchar(100) COLLATE utf16_unicode_ci NOT NULL,
  467.   `password` varchar(40) COLLATE utf16_unicode_ci NOT NULL,
  468.   `confirm_password` varchar(40) COLLATE utf16_unicode_ci NOT NULL,
  469.   `role` varchar(20) COLLATE utf16_unicode_ci NOT NULL,
  470.   `status` bit(1) NOT NULL DEFAULT b'0'
  471. ) ENGINE=InnoDB DEFAULT CHARSET=utf16 COLLATE=utf16_unicode_ci;
  472.  
  473. --
  474. -- Dumping data for table `parent_info`
  475. --
  476.  
  477. INSERT INTO `parent_info` (`parent_id`, `first_name`, `last_name`, `username`, `address`, `postal_code`, `city`, `state`, `home_phone`, `phone`, `emergency_contact_name`, `emergency_contact_number`, `email`, `password`, `confirm_password`, `role`, `status`) VALUES
  478. (39, 'n', 'n', 'nadimcse', 'n', 'n', 'n', 'NE', 'n', 'n', 'n', 'n', 'nadimcse.official@gmail.com', 'e10adc3949ba59abbe56e057f20f883e', '12345', 'user', b'1'),
  479. (48, 'k', 'k', 'k', 'k', 'k', 'k', 'KS', 'k', 'k', 'k', 'k', 'na146363@gmail.com', 'e10adc3949ba59abbe56e057f20f883e', 'k', 'user', b'0');
  480.  
  481. -- --------------------------------------------------------
  482.  
  483. --
  484. -- Table structure for table `product`
  485. --
  486.  
  487. CREATE TABLE `product` (
  488.   `id` int(11) NOT NULL,
  489.   `name` varchar(40) COLLATE utf16_unicode_ci NOT NULL,
  490.   `age` varchar(10) COLLATE utf16_unicode_ci NOT NULL,
  491.   `sports_type` varchar(20) COLLATE utf16_unicode_ci NOT NULL,
  492.   `price` float NOT NULL,
  493.   `qty` varchar(10) COLLATE utf16_unicode_ci NOT NULL,
  494.   `coach_name` varchar(30) COLLATE utf16_unicode_ci NOT NULL,
  495.   `overview` varchar(1000) COLLATE utf16_unicode_ci NOT NULL,
  496.   `image_path` varchar(100) COLLATE utf16_unicode_ci NOT NULL
  497. ) ENGINE=InnoDB DEFAULT CHARSET=utf16 COLLATE=utf16_unicode_ci;
  498.  
  499. --
  500. -- Dumping data for table `product`
  501. --
  502.  
  503. INSERT INTO `product` (`id`, `name`, `age`, `sports_type`, `price`, `qty`, `coach_name`, `overview`, `image_path`) VALUES
  504. (1, 'Toddler Group', '2-3', '', 120, '9', 'Tanyer Ahmed', 'Children between ages 2-3 years old will be introduced to essential soccer principles, such as using your feet, dribbling and the basic rules of the game. Involvement through fun games and positive support, children will become familiar to and experience the joy of playing soccer and being active.', 'uploads/products/images/1516589622592f4b6eebb42.jpgjpg'),
  505. (2, ' Mini Group', '4-6', '', 120, '5', 'Tanyer Ahmed', 'Children between ages 4-5 years old will be introduced to creative and imaginative games to focus on basic soccer skills like dribbling, passing and shooting. We also highlight a positive character trait each session such as respect, teamwork and appreciation.', 'uploads/products/images/543665935592f4b6f5b082.jpgjpg'),
  506. (3, 'Junior Group', '6-7', '', 120, '5', 'Tanyer Ahmed', 'Children between ages 6-7 years old will focus on individual skill, fitness and sportsmanship, providing an opportunity for children to be challenged through fun games and team interaction. Children will also be introduced to competition in a developmentally appropriate manner.', 'uploads/products/images/1503588273592f4b7167097.jpg');
  507.  
  508. -- --------------------------------------------------------
  509.  
  510. --
  511. -- Table structure for table `program_review`
  512. --
  513.  
  514. CREATE TABLE `program_review` (
  515.   `review_id` int(11) NOT NULL,
  516.   `fullname` varchar(45) NOT NULL,
  517.   `email` varchar(45) NOT NULL,
  518.   `review` varchar(1000) NOT NULL,
  519.   `rating` double NOT NULL,
  520.   `review_date` date NOT NULL
  521. ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
  522.  
  523. --
  524. -- Dumping data for table `program_review`
  525. --
  526.  
  527. INSERT INTO `program_review` (`review_id`, `fullname`, `email`, `review`, `rating`, `review_date`) VALUES
  528. (8, 'njasjndjdajn', 'ajnsjnadjns', 'asdjadjnjda', 0, '2017-07-11'),
  529. (9, 'asdasda', 'asdasd', 'sadasda', 0, '2017-07-11'),
  530. (10, 'sadada', 'asdasda', 'asdad', 0, '2017-07-11'),
  531. (11, 'Nadim', 'na146363@gmail.com', 'Hello', 4.5, '2017-07-12'),
  532. (12, 'nad', 'na@g.com', 'hi', 3, '2017-07-12');
  533.  
  534. -- --------------------------------------------------------
  535.  
  536. --
  537. -- Table structure for table `tokens`
  538. --
  539.  
  540. CREATE TABLE `tokens` (
  541.   `parent_id` int(11) NOT NULL,
  542.   `token` varchar(200) COLLATE utf16_unicode_ci NOT NULL,
  543.   `created` date NOT NULL
  544. ) ENGINE=InnoDB DEFAULT CHARSET=utf16 COLLATE=utf16_unicode_ci;
  545.  
  546. --
  547. -- Dumping data for table `tokens`
  548. --
  549.  
  550. INSERT INTO `tokens` (`parent_id`, `token`, `created`) VALUES
  551. (48, '02fc0cfa2e01a4c1635760137f1a07', '2017-06-01'),
  552. (48, '02e8f10166119f8de64e8232da2b43', '2017-06-01');
  553.  
  554. --
  555. -- Indexes for dumped tables
  556. --
  557.  
  558. --
  559. -- Indexes for table `admin`
  560. --
  561. ALTER TABLE `admin`
  562.   ADD PRIMARY KEY (`id`);
  563.  
  564. --
  565. -- Indexes for table `child_info`
  566. --
  567. ALTER TABLE `child_info`
  568.   ADD PRIMARY KEY (`child_id`);
  569.  
  570. --
  571. -- Indexes for table `classes`
  572. --
  573. ALTER TABLE `classes`
  574.   ADD PRIMARY KEY (`class_id`);
  575.  
  576. --
  577. -- Indexes for table `class_request`
  578. --
  579. ALTER TABLE `class_request`
  580.   ADD PRIMARY KEY (`request_id`);
  581.  
  582. --
  583. -- Indexes for table `coach`
  584. --
  585. ALTER TABLE `coach`
  586.   ADD PRIMARY KEY (`id`);
  587.  
  588. --
  589. -- Indexes for table `contact_page`
  590. --
  591. ALTER TABLE `contact_page`
  592.   ADD PRIMARY KEY (`id`);
  593.  
  594. --
  595. -- Indexes for table `customers`
  596. --
  597. ALTER TABLE `customers`
  598.   ADD PRIMARY KEY (`customerid`);
  599.  
  600. --
  601. -- Indexes for table `gallery`
  602. --
  603. ALTER TABLE `gallery`
  604.   ADD PRIMARY KEY (`image_id`);
  605.  
  606. --
  607. -- Indexes for table `news`
  608. --
  609. ALTER TABLE `news`
  610.   ADD PRIMARY KEY (`news_id`);
  611.  
  612. --
  613. -- Indexes for table `orders`
  614. --
  615. ALTER TABLE `orders`
  616.   ADD PRIMARY KEY (`serial`);
  617.  
  618. --
  619. -- Indexes for table `parent_info`
  620. --
  621. ALTER TABLE `parent_info`
  622.   ADD PRIMARY KEY (`parent_id`);
  623.  
  624. --
  625. -- Indexes for table `program_review`
  626. --
  627. ALTER TABLE `program_review`
  628.   ADD PRIMARY KEY (`review_id`);
  629.  
  630. --
  631. -- AUTO_INCREMENT for dumped tables
  632. --
  633.  
  634. --
  635. -- AUTO_INCREMENT for table `admin`
  636. --
  637. ALTER TABLE `admin`
  638.   MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;
  639. --
  640. -- AUTO_INCREMENT for table `child_info`
  641. --
  642. ALTER TABLE `child_info`
  643.   MODIFY `child_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=52;
  644. --
  645. -- AUTO_INCREMENT for table `classes`
  646. --
  647. ALTER TABLE `classes`
  648.   MODIFY `class_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=23;
  649. --
  650. -- AUTO_INCREMENT for table `class_request`
  651. --
  652. ALTER TABLE `class_request`
  653.   MODIFY `request_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=22;
  654. --
  655. -- AUTO_INCREMENT for table `coach`
  656. --
  657. ALTER TABLE `coach`
  658.   MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6;
  659. --
  660. -- AUTO_INCREMENT for table `contact_page`
  661. --
  662. ALTER TABLE `contact_page`
  663.   MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=25;
  664. --
  665. -- AUTO_INCREMENT for table `customers`
  666. --
  667. ALTER TABLE `customers`
  668.   MODIFY `customerid` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=23;
  669. --
  670. -- AUTO_INCREMENT for table `gallery`
  671. --
  672. ALTER TABLE `gallery`
  673.   MODIFY `image_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=20;
  674. --
  675. -- AUTO_INCREMENT for table `news`
  676. --
  677. ALTER TABLE `news`
  678.   MODIFY `news_id` int(11) NOT NULL AUTO_INCREMENT;
  679. --
  680. -- AUTO_INCREMENT for table `orders`
  681. --
  682. ALTER TABLE `orders`
  683.   MODIFY `serial` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=23;
  684. --
  685. -- AUTO_INCREMENT for table `parent_info`
  686. --
  687. ALTER TABLE `parent_info`
  688.   MODIFY `parent_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=49;
  689. --
  690. -- AUTO_INCREMENT for table `program_review`
  691. --
  692. ALTER TABLE `program_review`
  693.   MODIFY `review_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=13;
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!