Advertisement
Guest User

Untitled

a guest
Oct 25th, 2018
202
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 15.04 KB | None | 0 0
  1. -- phpMyAdmin SQL Dump
  2. -- version 4.7.3
  3. -- https://www.phpmyadmin.net/
  4. --
  5. -- Host: localhost:3306
  6. -- Generation Time: Oct 25, 2018 at 11:55 PM
  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: `project_board`
  15. --
  16.  
  17. -- --------------------------------------------------------
  18.  
  19. --
  20. -- Table structure for table `admin_table`
  21. --
  22.  
  23. CREATE TABLE `admin_table` (
  24. `admin_id` int(11) NOT NULL,
  25. `admin_username` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  26. `admin_email` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  27. `admin_password` varchar(1000) COLLATE utf8mb4_unicode_ci NOT NULL,
  28. `role` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL
  29. ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  30.  
  31. --
  32. -- Dumping data for table `admin_table`
  33. --
  34.  
  35. INSERT INTO `admin_table` (`admin_id`, `admin_username`, `admin_email`, `admin_password`, `role`) VALUES
  36. (1, 'admin', 'admin@gmail.com', 'e10adc3949ba59abbe56e057f20f883e', 'admin');
  37.  
  38. -- --------------------------------------------------------
  39.  
  40. --
  41. -- Table structure for table `file`
  42. --
  43.  
  44. CREATE TABLE `file` (
  45. `f_id` int(11) NOT NULL,
  46. `file_title` varchar(255) COLLATE utf32_unicode_ci NOT NULL,
  47. `proposal_id` int(11) NOT NULL,
  48. `file_path` varchar(1000) COLLATE utf32_unicode_ci NOT NULL,
  49. `file_type` varchar(50) COLLATE utf32_unicode_ci NOT NULL,
  50. `uploaded_by` int(11) NOT NULL,
  51. `create_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  52. `file_details` varchar(1000) COLLATE utf32_unicode_ci NOT NULL
  53. ) ENGINE=InnoDB DEFAULT CHARSET=utf32 COLLATE=utf32_unicode_ci;
  54.  
  55. --
  56. -- Dumping data for table `file`
  57. --
  58.  
  59. INSERT INTO `file` (`f_id`, `file_title`, `proposal_id`, `file_path`, `file_type`, `uploaded_by`, `create_at`, `file_details`) VALUES
  60. (1, 'This is title ', 1, 'http://localhost/project-board(v3)/uploads/7ccd560ba2852de378c4efff5086fad9.pdf', 'pdf', 1203020005, '2018-10-22 10:06:18', 'This is details '),
  61. (2, 'This is title 2', 1, 'http://localhost/project-board(v3)/uploads/c886e5a4c495156ed486e1d6bb112dc6.jpg', 'jpg', 1203020005, '2018-10-22 10:06:52', 'This is details 2 ');
  62.  
  63. -- --------------------------------------------------------
  64.  
  65. --
  66. -- Table structure for table `link`
  67. --
  68.  
  69. CREATE TABLE `link` (
  70. `linkid` int(11) NOT NULL,
  71. `link_title` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  72. `link_url` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  73. `student_id` int(11) NOT NULL,
  74. `proposal_id` int(11) NOT NULL,
  75. `link_create_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP
  76. ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  77.  
  78. --
  79. -- Dumping data for table `link`
  80. --
  81.  
  82. INSERT INTO `link` (`linkid`, `link_title`, `link_url`, `student_id`, `proposal_id`, `link_create_at`) VALUES
  83. (1, 'My link', 'https://nadimlu.github.io/hamdard/index.html', 1203020005, 1, '2018-10-22 10:05:27');
  84.  
  85. -- --------------------------------------------------------
  86.  
  87. --
  88. -- Table structure for table `proposal`
  89. --
  90.  
  91. CREATE TABLE `proposal` (
  92. `proposal_id` int(11) NOT NULL,
  93. `t_id` int(11) NOT NULL,
  94. `project_name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  95. `project_cat` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  96. `course_code` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  97. `project_abstract` varchar(1000) COLLATE utf8mb4_unicode_ci NOT NULL,
  98. `project_objective` varchar(1000) COLLATE utf8mb4_unicode_ci NOT NULL,
  99. `project_features` varchar(1000) COLLATE utf8mb4_unicode_ci NOT NULL,
  100. `project_modules` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  101. `project_tools` varchar(1000) COLLATE utf8mb4_unicode_ci NOT NULL,
  102. `project_conclusion` varchar(1000) COLLATE utf8mb4_unicode_ci NOT NULL,
  103. `request_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  104. `accepted_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  105. `rejected_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  106. `project_status` tinyint(1) NOT NULL,
  107. `is_reffered` varchar(10) COLLATE utf8mb4_unicode_ci NOT NULL,
  108. `t_comment` varchar(1000) COLLATE utf8mb4_unicode_ci NOT NULL
  109. ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  110.  
  111. --
  112. -- Dumping data for table `proposal`
  113. --
  114.  
  115. INSERT INTO `proposal` (`proposal_id`, `t_id`, `project_name`, `project_cat`, `course_code`, `project_abstract`, `project_objective`, `project_features`, `project_modules`, `project_tools`, `project_conclusion`, `request_time`, `accepted_at`, `rejected_at`, `project_status`, `is_reffered`, `t_comment`) VALUES
  116. (1, 1, 'Facebook Clone', 'Web Application Development', 'CSE-4400', '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 publishing software like Aldus PageMaker including versions of Lorem Ipsum', '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 publishing software like Aldus PageMaker including versions of Lorem Ipsum', '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 publishing software like Aldus PageMaker including versions of Lorem Ipsum', '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 su', '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 publishing software like Aldus PageMaker including versions of Lorem Ipsum', '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 publishing software like Aldus PageMaker including versions of Lorem Ipsum', '2018-10-17 10:54:42', '2018-10-17 10:56:44', '2018-10-17 10:54:42', 1, '', 'This is a good Project ');
  117.  
  118. -- --------------------------------------------------------
  119.  
  120. --
  121. -- Table structure for table `referred_proposals`
  122. --
  123.  
  124. CREATE TABLE `referred_proposals` (
  125. `r_p_id` int(11) NOT NULL,
  126. `t_id` int(11) NOT NULL,
  127. `proposal_id` int(11) NOT NULL,
  128. `refered_time` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL
  129. ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  130.  
  131. -- --------------------------------------------------------
  132.  
  133. --
  134. -- Table structure for table `student`
  135. --
  136.  
  137. CREATE TABLE `student` (
  138. `m_id` int(11) NOT NULL,
  139. `proposal_id` int(11) NOT NULL,
  140. `member_name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  141. `member_email` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  142. `member_student_id` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  143. `team_leader` int(11) NOT NULL,
  144. `member_mobile_no` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  145. `password` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  146. `role` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  147. `created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  148. `status` varchar(24) COLLATE utf8mb4_unicode_ci NOT NULL
  149. ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  150.  
  151. --
  152. -- Dumping data for table `student`
  153. --
  154.  
  155. INSERT INTO `student` (`m_id`, `proposal_id`, `member_name`, `member_email`, `member_student_id`, `team_leader`, `member_mobile_no`, `password`, `role`, `created_at`, `status`) VALUES
  156. (1, 1, 'Nadim', 'na146363@gmail.com', '1203020005', 0, '01731001333', 'e10adc3949ba59abbe56e057f20f883e', 'student', '2018-10-17 10:58:07', '1'),
  157. (2, 1, 'Shuvo Roy', 'shuvo@gmail.com', '1203020006', 0, '01671146363', 'e10adc3949ba59abbe56e057f20f883e', 'student', '2018-10-17 10:58:09', '1');
  158.  
  159. -- --------------------------------------------------------
  160.  
  161. --
  162. -- Table structure for table `student_email`
  163. --
  164.  
  165. CREATE TABLE `student_email` (
  166. `id` int(11) NOT NULL,
  167. `student_id` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL,
  168. `student_email` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL,
  169. `status` int(11) NOT NULL
  170. ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  171.  
  172. --
  173. -- Dumping data for table `student_email`
  174. --
  175.  
  176. INSERT INTO `student_email` (`id`, `student_id`, `student_email`, `status`) VALUES
  177. (1, '1203020005', 'na146363@gmail.com', 0),
  178. (2, '1203020006', 'shuvo@gmail.com', 0);
  179.  
  180. -- --------------------------------------------------------
  181.  
  182. --
  183. -- Table structure for table `sub_task`
  184. --
  185.  
  186. CREATE TABLE `sub_task` (
  187. `subtask_id` int(11) NOT NULL,
  188. `task_id` int(11) NOT NULL,
  189. `subtask_headline` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  190. `subtask_details` varchar(1000) COLLATE utf8mb4_unicode_ci NOT NULL,
  191. `subcreate_at` datetime NOT NULL,
  192. `subtask_status` int(11) NOT NULL
  193. ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  194.  
  195. --
  196. -- Dumping data for table `sub_task`
  197. --
  198.  
  199. INSERT INTO `sub_task` (`subtask_id`, `task_id`, `subtask_headline`, `subtask_details`, `subcreate_at`, `subtask_status`) VALUES
  200. (1, 1, 'This is sub task', 'this is details', '2018-10-24 15:49:18', 0);
  201.  
  202. -- --------------------------------------------------------
  203.  
  204. --
  205. -- Table structure for table `task`
  206. --
  207.  
  208. CREATE TABLE `task` (
  209. `task_id` int(11) NOT NULL,
  210. `task_headline` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  211. `task_details` varchar(1000) COLLATE utf8mb4_unicode_ci NOT NULL,
  212. `t_id` int(11) NOT NULL,
  213. `proposal_id` int(11) NOT NULL,
  214. `create_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  215. `completed_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  216. `task_status` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL
  217. ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  218.  
  219. --
  220. -- Dumping data for table `task`
  221. --
  222.  
  223. INSERT INTO `task` (`task_id`, `task_headline`, `task_details`, `t_id`, `proposal_id`, `create_at`, `completed_at`, `task_status`) VALUES
  224. (1, 'This is task 1', 'THIS IS TASK ONE ', 1, 1, '2018-10-17 11:08:23', '2018-10-17 11:08:23', '0');
  225.  
  226. -- --------------------------------------------------------
  227.  
  228. --
  229. -- Table structure for table `teachers`
  230. --
  231.  
  232. CREATE TABLE `teachers` (
  233. `t_id` int(11) UNSIGNED NOT NULL,
  234. `t_name` varchar(255) DEFAULT NULL,
  235. `t_email` varchar(255) NOT NULL,
  236. `t_password` varchar(255) NOT NULL,
  237. `role` varchar(255) NOT NULL,
  238. `t_post` varchar(255) NOT NULL,
  239. `t_mobile` varchar(255) NOT NULL,
  240. `status` int(11) NOT NULL COMMENT '1 for Active , 2 for Inactive',
  241. `created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP
  242. ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
  243.  
  244. --
  245. -- Dumping data for table `teachers`
  246. --
  247.  
  248. INSERT INTO `teachers` (`t_id`, `t_name`, `t_email`, `t_password`, `role`, `t_post`, `t_mobile`, `status`, `created_at`) VALUES
  249. (1, 'Nadim', 'na146363@gmail.com', 'e10adc3949ba59abbe56e057f20f883e', 'teacher', 'Lecturer', '01731001333', 1, '2018-10-17 10:52:20');
  250.  
  251. --
  252. -- Indexes for dumped tables
  253. --
  254.  
  255. --
  256. -- Indexes for table `admin_table`
  257. --
  258. ALTER TABLE `admin_table`
  259. ADD PRIMARY KEY (`admin_id`);
  260.  
  261. --
  262. -- Indexes for table `file`
  263. --
  264. ALTER TABLE `file`
  265. ADD PRIMARY KEY (`f_id`);
  266.  
  267. --
  268. -- Indexes for table `link`
  269. --
  270. ALTER TABLE `link`
  271. ADD PRIMARY KEY (`linkid`);
  272.  
  273. --
  274. -- Indexes for table `proposal`
  275. --
  276. ALTER TABLE `proposal`
  277. ADD PRIMARY KEY (`proposal_id`);
  278.  
  279. --
  280. -- Indexes for table `referred_proposals`
  281. --
  282. ALTER TABLE `referred_proposals`
  283. ADD PRIMARY KEY (`r_p_id`);
  284.  
  285. --
  286. -- Indexes for table `student`
  287. --
  288. ALTER TABLE `student`
  289. ADD PRIMARY KEY (`m_id`);
  290.  
  291. --
  292. -- Indexes for table `student_email`
  293. --
  294. ALTER TABLE `student_email`
  295. ADD PRIMARY KEY (`id`);
  296.  
  297. --
  298. -- Indexes for table `sub_task`
  299. --
  300. ALTER TABLE `sub_task`
  301. ADD PRIMARY KEY (`subtask_id`);
  302.  
  303. --
  304. -- Indexes for table `task`
  305. --
  306. ALTER TABLE `task`
  307. ADD PRIMARY KEY (`task_id`);
  308.  
  309. --
  310. -- Indexes for table `teachers`
  311. --
  312. ALTER TABLE `teachers`
  313. ADD PRIMARY KEY (`t_id`);
  314.  
  315. --
  316. -- AUTO_INCREMENT for dumped tables
  317. --
  318.  
  319. --
  320. -- AUTO_INCREMENT for table `admin_table`
  321. --
  322. ALTER TABLE `admin_table`
  323. MODIFY `admin_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
  324. --
  325. -- AUTO_INCREMENT for table `file`
  326. --
  327. ALTER TABLE `file`
  328. MODIFY `f_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
  329. --
  330. -- AUTO_INCREMENT for table `link`
  331. --
  332. ALTER TABLE `link`
  333. MODIFY `linkid` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
  334. --
  335. -- AUTO_INCREMENT for table `proposal`
  336. --
  337. ALTER TABLE `proposal`
  338. MODIFY `proposal_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
  339. --
  340. -- AUTO_INCREMENT for table `referred_proposals`
  341. --
  342. ALTER TABLE `referred_proposals`
  343. MODIFY `r_p_id` int(11) NOT NULL AUTO_INCREMENT;
  344. --
  345. -- AUTO_INCREMENT for table `student`
  346. --
  347. ALTER TABLE `student`
  348. MODIFY `m_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
  349. --
  350. -- AUTO_INCREMENT for table `student_email`
  351. --
  352. ALTER TABLE `student_email`
  353. MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
  354. --
  355. -- AUTO_INCREMENT for table `sub_task`
  356. --
  357. ALTER TABLE `sub_task`
  358. MODIFY `subtask_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
  359. --
  360. -- AUTO_INCREMENT for table `task`
  361. --
  362. ALTER TABLE `task`
  363. MODIFY `task_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
  364. --
  365. -- AUTO_INCREMENT for table `teachers`
  366. --
  367. ALTER TABLE `teachers`
  368. MODIFY `t_id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement