745212572c
24012023
478 lines
21 KiB
SQL
478 lines
21 KiB
SQL
-- phpMyAdmin SQL Dump
|
||
-- version 5.2.0
|
||
-- https://www.phpmyadmin.net/
|
||
--
|
||
-- Host: 127.0.0.1
|
||
-- Generation Time: Jan 24, 2023 at 11:03 AM
|
||
-- Server version: 10.4.24-MariaDB
|
||
-- PHP Version: 7.4.29
|
||
|
||
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
|
||
START TRANSACTION;
|
||
SET time_zone = "+00:00";
|
||
|
||
|
||
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
|
||
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
|
||
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
|
||
/*!40101 SET NAMES utf8mb4 */;
|
||
|
||
--
|
||
-- Database: `mcgans`
|
||
--
|
||
|
||
-- --------------------------------------------------------
|
||
|
||
--
|
||
-- Table structure for table `degree`
|
||
--
|
||
|
||
CREATE TABLE `degree` (
|
||
`id` int(11) NOT NULL,
|
||
`departmentId` int(11) NOT NULL,
|
||
`name` varchar(225) NOT NULL,
|
||
`createdBy` int(11) NOT NULL,
|
||
`createdOn` date NOT NULL,
|
||
`upadatedOn` date NOT NULL,
|
||
`updatedBy` int(11) NOT NULL,
|
||
`status` int(11) NOT NULL
|
||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
|
||
|
||
--
|
||
-- Dumping data for table `degree`
|
||
--
|
||
|
||
INSERT INTO `degree` (`id`, `departmentId`, `name`, `createdBy`, `createdOn`, `upadatedOn`, `updatedBy`, `status`) VALUES
|
||
(1, 1, 'Bachelor’s in Architecture', 1, '2023-01-23', '0000-00-00', 0, 1);
|
||
|
||
-- --------------------------------------------------------
|
||
|
||
--
|
||
-- Table structure for table `department`
|
||
--
|
||
|
||
CREATE TABLE `department` (
|
||
`id` int(11) NOT NULL,
|
||
`name` varchar(225) NOT NULL,
|
||
`code` varchar(100) NOT NULL,
|
||
`image` varchar(225) NOT NULL,
|
||
`year` int(11) NOT NULL,
|
||
`createdBy` int(11) NOT NULL,
|
||
`updatedBy` int(11) NOT NULL,
|
||
`createdOn` date NOT NULL,
|
||
`updatedOn` date NOT NULL,
|
||
`status` int(11) NOT NULL
|
||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
|
||
|
||
--
|
||
-- Dumping data for table `department`
|
||
--
|
||
|
||
INSERT INTO `department` (`id`, `name`, `code`, `image`, `year`, `createdBy`, `updatedBy`, `createdOn`, `updatedOn`, `status`) VALUES
|
||
(1, 'Architecture', 'AR001', '230123053918.webp', 4, 1, 0, '2023-01-23', '0000-00-00', 1);
|
||
|
||
-- --------------------------------------------------------
|
||
|
||
--
|
||
-- Table structure for table `employee`
|
||
--
|
||
|
||
CREATE TABLE `employee` (
|
||
`id` int(11) NOT NULL,
|
||
`roleId` int(11) NOT NULL,
|
||
`name` varchar(120) NOT NULL,
|
||
`mobileNumber` varchar(225) NOT NULL,
|
||
`address` text NOT NULL,
|
||
`email` varchar(225) NOT NULL,
|
||
`image` varchar(225) NOT NULL,
|
||
`pincode` int(11) NOT NULL,
|
||
`username` varchar(225) NOT NULL,
|
||
`password` varchar(225) NOT NULL,
|
||
`createdOn` date NOT NULL,
|
||
`updatedOn` date NOT NULL,
|
||
`createdBy` int(11) NOT NULL,
|
||
`updatedBy` int(11) NOT NULL,
|
||
`status` int(1) NOT NULL
|
||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
|
||
|
||
--
|
||
-- Dumping data for table `employee`
|
||
--
|
||
|
||
INSERT INTO `employee` (`id`, `roleId`, `name`, `mobileNumber`, `address`, `email`, `image`, `pincode`, `username`, `password`, `createdOn`, `updatedOn`, `createdBy`, `updatedBy`, `status`) VALUES
|
||
(1, 1, 'mcgans', '9344511168', 'Perar, Kotagiri Road, Ooty, Tamil Nadu 643002', 'ootyarchitecture@gmail.com', 'image.png', 643002, 'demo@mcgans.com', '2d1c52a7d892a6f0a189392152584268', '0000-00-00', '0000-00-00', 0, 0, 1);
|
||
|
||
-- --------------------------------------------------------
|
||
|
||
--
|
||
-- Table structure for table `faculty`
|
||
--
|
||
|
||
CREATE TABLE `faculty` (
|
||
`id` int(11) NOT NULL,
|
||
`facultyId` varchar(225) NOT NULL,
|
||
`name` varchar(225) NOT NULL,
|
||
`email` varchar(100) NOT NULL,
|
||
`dob` date NOT NULL,
|
||
`address` text NOT NULL,
|
||
`gender` int(11) NOT NULL,
|
||
`mobileNumber` varchar(225) NOT NULL,
|
||
`designation` varchar(225) NOT NULL,
|
||
`image` text NOT NULL,
|
||
`createdBy` int(11) NOT NULL,
|
||
`createdOn` date NOT NULL,
|
||
`updatedOn` date NOT NULL,
|
||
`updatedBy` int(11) NOT NULL,
|
||
`status` int(11) NOT NULL
|
||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
|
||
|
||
--
|
||
-- Dumping data for table `faculty`
|
||
--
|
||
|
||
INSERT INTO `faculty` (`id`, `facultyId`, `name`, `email`, `dob`, `address`, `gender`, `mobileNumber`, `designation`, `image`, `createdBy`, `createdOn`, `updatedOn`, `updatedBy`, `status`) VALUES
|
||
(1, 'MCGANS0001', 'Saranya SK', 'mcgans@gmail.com', '2023-01-23', 'Ooty', 2, '7904257993', 'Staff', '2301230548.webp', 1, '2023-01-23', '0000-00-00', 0, 1),
|
||
(2, 'MCGANS0002', 'Kshirabdhi Tanaya P Sahu', 'mcgans@gmail.com', '2023-01-23', 'Ooty', 2, '7904257993', 'Staff', '2301230551.webp', 1, '2023-01-23', '0000-00-00', 0, 1),
|
||
(3, 'MCGANS0003', 'Lokeshwar', 'mcgans@gmail.com', '2023-01-23', 'Ooty', 1, '7904257993', 'Staff', '2301230553.webp', 1, '2023-01-23', '0000-00-00', 0, 1),
|
||
(4, 'MCGANS0004', 'Srinath', 'mcgans@gmail.com', '2023-01-23', 'Ooty', 1, '7904257993', 'Staff', '2301230555.webp', 1, '2023-01-23', '0000-00-00', 0, 1),
|
||
(5, 'MCGANS0005', 'Shahzad Ahmed Malik', 'mcgans@gmail.com', '2023-01-23', 'Ooty', 1, '7904257993', 'Staff', '2301230603.webp', 1, '2023-01-23', '0000-00-00', 0, 1);
|
||
|
||
-- --------------------------------------------------------
|
||
|
||
--
|
||
-- Table structure for table `project`
|
||
--
|
||
|
||
CREATE TABLE `project` (
|
||
`id` int(11) NOT NULL,
|
||
`projectName` varchar(225) NOT NULL,
|
||
`date` date NOT NULL,
|
||
`studentId` int(11) NOT NULL,
|
||
`code` varchar(225) NOT NULL,
|
||
`semesterId` int(11) NOT NULL,
|
||
`departmentId` int(11) NOT NULL,
|
||
`description` text NOT NULL,
|
||
`subjectId` int(11) NOT NULL,
|
||
`image` text NOT NULL,
|
||
`vedio` varchar(300) NOT NULL,
|
||
`driveLink` varchar(300) NOT NULL,
|
||
`createdBy` int(11) NOT NULL,
|
||
`createdOn` date NOT NULL,
|
||
`updatedBy` int(11) NOT NULL,
|
||
`updatedOn` date NOT NULL,
|
||
`status` int(11) NOT NULL
|
||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
|
||
|
||
--
|
||
-- Dumping data for table `project`
|
||
--
|
||
|
||
INSERT INTO `project` (`id`, `projectName`, `date`, `studentId`, `code`, `semesterId`, `departmentId`, `description`, `subjectId`, `image`, `vedio`, `driveLink`, `createdBy`, `createdOn`, `updatedBy`, `updatedOn`, `status`) VALUES
|
||
(1, 'Testtt', '2023-01-25', 1, 'P001tt', 3, 1, 'testttttt', 1, 'title230124102722.jpg', 'testtt', 'testtt', 1, '2023-01-24', 1, '2023-01-24', 1);
|
||
|
||
-- --------------------------------------------------------
|
||
|
||
--
|
||
-- Table structure for table `projectdetail`
|
||
--
|
||
|
||
CREATE TABLE `projectdetail` (
|
||
`id` int(11) NOT NULL,
|
||
`projectId` int(11) NOT NULL,
|
||
`title` varchar(225) NOT NULL,
|
||
`image` varchar(225) NOT NULL,
|
||
`status` int(11) NOT NULL
|
||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
|
||
|
||
--
|
||
-- Dumping data for table `projectdetail`
|
||
--
|
||
|
||
INSERT INTO `projectdetail` (`id`, `projectId`, `title`, `image`, `status`) VALUES
|
||
(1, 1, 'test12', '1.5.jpg', 1),
|
||
(2, 1, 'test112', '1.4.jpg', 1),
|
||
(3, 1, 'test3', '1.1.jpg', 0);
|
||
|
||
-- --------------------------------------------------------
|
||
|
||
--
|
||
-- Table structure for table `role`
|
||
--
|
||
|
||
CREATE TABLE `role` (
|
||
`id` int(11) NOT NULL,
|
||
`name` varchar(120) NOT NULL,
|
||
`status` int(11) NOT NULL,
|
||
`createdBy` int(11) NOT NULL,
|
||
`createdOn` date NOT NULL,
|
||
`updatedBy` int(11) NOT NULL,
|
||
`updatedOn` date NOT NULL
|
||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
|
||
|
||
--
|
||
-- Dumping data for table `role`
|
||
--
|
||
|
||
INSERT INTO `role` (`id`, `name`, `status`, `createdBy`, `createdOn`, `updatedBy`, `updatedOn`) VALUES
|
||
(1, 'admin', 1, 1, '2023-01-23', 0, '0000-00-00');
|
||
|
||
-- --------------------------------------------------------
|
||
|
||
--
|
||
-- Table structure for table `semester`
|
||
--
|
||
|
||
CREATE TABLE `semester` (
|
||
`id` int(11) NOT NULL,
|
||
`name` varchar(225) NOT NULL,
|
||
`year` int(11) NOT NULL,
|
||
`subjectId` varchar(225) NOT NULL,
|
||
`departmentId` int(11) NOT NULL,
|
||
`degreeId` int(11) NOT NULL,
|
||
`createdBy` int(11) NOT NULL,
|
||
`createdOn` date NOT NULL,
|
||
`updatedOn` date NOT NULL,
|
||
`updatedBy` int(11) NOT NULL,
|
||
`status` int(11) NOT NULL
|
||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
|
||
|
||
--
|
||
-- Dumping data for table `semester`
|
||
--
|
||
|
||
INSERT INTO `semester` (`id`, `name`, `year`, `subjectId`, `departmentId`, `degreeId`, `createdBy`, `createdOn`, `updatedOn`, `updatedBy`, `status`) VALUES
|
||
(3, 'EVEN', 2023, '1,2,3,4,5', 1, 1, 1, '2023-01-23', '2023-01-23', 1, 1);
|
||
|
||
-- --------------------------------------------------------
|
||
|
||
--
|
||
-- Table structure for table `student`
|
||
--
|
||
|
||
CREATE TABLE `student` (
|
||
`id` int(11) NOT NULL,
|
||
`studentId` varchar(225) NOT NULL,
|
||
`name` varchar(225) NOT NULL,
|
||
`gender` int(11) NOT NULL,
|
||
`email` varchar(100) NOT NULL,
|
||
`address` text NOT NULL,
|
||
`department` varchar(225) NOT NULL,
|
||
`mobileNumber` varchar(225) NOT NULL,
|
||
`dob` date NOT NULL,
|
||
`image` varchar(225) NOT NULL,
|
||
`updatedOn` date NOT NULL,
|
||
`updatedBy` int(11) NOT NULL,
|
||
`createdBy` int(11) NOT NULL,
|
||
`createdOn` date NOT NULL,
|
||
`status` int(11) NOT NULL
|
||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
|
||
|
||
--
|
||
-- Dumping data for table `student`
|
||
--
|
||
|
||
INSERT INTO `student` (`id`, `studentId`, `name`, `gender`, `email`, `address`, `department`, `mobileNumber`, `dob`, `image`, `updatedOn`, `updatedBy`, `createdBy`, `createdOn`, `status`) VALUES
|
||
(1, '0001', 'test', 1, 'test@gmail.com', 'test', '1', '9876543210', '2023-01-03', '2301240937.png', '0000-00-00', 0, 1, '2023-01-24', 1);
|
||
|
||
-- --------------------------------------------------------
|
||
|
||
--
|
||
-- Table structure for table `subject`
|
||
--
|
||
|
||
CREATE TABLE `subject` (
|
||
`id` int(11) NOT NULL,
|
||
`degreeId` int(11) NOT NULL,
|
||
`name` varchar(225) NOT NULL,
|
||
`code` varchar(225) NOT NULL,
|
||
`facultyId` varchar(225) NOT NULL,
|
||
`image` varchar(225) NOT NULL,
|
||
`description` longtext NOT NULL,
|
||
`createdBy` int(11) NOT NULL,
|
||
`updatedBy` int(11) NOT NULL,
|
||
`createdOn` date NOT NULL,
|
||
`updatedOn` date NOT NULL,
|
||
`status` int(11) NOT NULL
|
||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
|
||
|
||
--
|
||
-- Dumping data for table `subject`
|
||
--
|
||
|
||
INSERT INTO `subject` (`id`, `degreeId`, `name`, `code`, `facultyId`, `image`, `description`, `createdBy`, `updatedBy`, `createdOn`, `updatedOn`, `status`) VALUES
|
||
(1, 1, ' Terrain and Architecture', 'MCL2001', '1', '230123064458.webp', 'The Anthropogenic Activities which require Space Making on any parcel of land, in terms \r\nof Open & Built Volumes has an interference with the existing natural landscape and the \r\necology connected therewith. Also in the current day context, the Virtue of a Terrain and \r\nits primary role of sustaining an ecosystem in order is often ignored while designing, \r\norganizing and constructing a Building.\r\nCritical Re-thinking on the Spatial Planning & Organization in any given Terrain is \r\nessential, today. Therefore, standard practice of Grading and Sitting Buildings on a \r\nLandscape by considering it to be an independent entity, needs to be recast to create a \r\nmeaningful articulation of Spaces with respect to a Terrain.\r\nIn this project we will deal with two Sites in the context of The Nilgiris District which are \r\ndifferent from one another primarily in terms of Altitude & Gradient and other related \r\naspects of Climate & Geography. Thus, comparing and demonstrating how planning \r\nstrategies vary.', 1, 1, '2023-01-23', '2023-01-24', 1),
|
||
(2, 1, 'Planning and Organizing Spatial organization in Architecture', 'MCL2002', '2', '230123064624.webp', 'Spatial Organization is a way to tie the spaces together to create a collective and \r\norganized whole. This can be done both on the micro-level with the floor plan zoning and \r\nat the macro level on the site.\r\nIn the period of 14 weeks, the first 3 weeks the student will work on design thinking \r\nmodule and remaining weeks develop continuously their design project. The design \r\nprocess make use of 5 steps design process (problem analysis, idea generation, idea \r\nevaluation and selection and the realization of ideas). The design studio aims to create a \r\nplan with these 5 steps to address concrete spatial issues on different scales and layouts \r\nin a predefined project site.\r\nFor every building, there are specific needs that need to be fulfilled. Spatial organization \r\ncan aid in problem-solving to come up with effective design solutions in terms of:\r\n• Zoning based on the needs of the site.\r\n• Functional segregation of spaces in the design.\r\n• Dimensional requirements of each space.\r\n• Organization based on the significance of each space.', 1, 0, '2023-01-23', '0000-00-00', 1),
|
||
(3, 1, 'Planning and Organizing The clash of the weathers', 'MCL2003', '3', '230123064720.webp', '“Mother art is Architecture. Without an architecture of our own we have no soul of our \r\nown civilization” – Frank Lloyd Wright.\r\nIn early times when humans started to settle, they needed a dwelling to cope up with the \r\nchanging weather of the location (climate), this is the time architecture started in them in \r\norder to resist the climate. Later civilizations happened where buildings were evolving to \r\nbe stronger and additional details were added to it to make it more responsive to climate. \r\nNow we can come to an understanding that humans started the concept of architecture \r\nin order to respond to the climate, but now days that priority is lacking in the majority \r\nof the population and they are forced to go against the nature. By building structures \r\nin a climate responsive manner, we can make the best use of the natural and renewable \r\nresources and reduce our dependency on non-renewable resources. \r\nIn this studio the students will be focusing on gaining an understanding in climate \r\nresponsive architecture by starting to design from a basic temporary structure parallelly \r\nlearn climatology concepts and go further to design a building typologyby exploring \r\nvarious forms, building elements, spatial planning and materials.', 1, 0, '2023-01-23', '0000-00-00', 1),
|
||
(4, 1, 'Constructing and Specifying Express it Industrially', 'MCL2004', '4', '230123064826.webp', 'Why a place that was once recognized and considered proud should be left useless? \r\nCities are already experiencing the shortage of lands for developments. Recycling has \r\nevolved to its ultimate level of converting most of the wastes generated today. Why \r\nnot a building could be recycled or renewed to serve its purpose or used for a different \r\npurpose? Cities of today have such buildings that could have lost its cultural, economic \r\nand social values over time. It is our duty to payback respects and restore their values \r\nthrough Adaptive Reuse. Here to make it more interesting, the students will be exposed \r\nto Industrial Architecture for adopting them into their designing. \r\nThe studio invites students for Re-imagining abandoned buildings in the vicinity, into a \r\npublic space. Throughout the Design Development process, students will be put into the \r\ncircumstances of questioning themselves on how to bridge the gap between the new \r\nneeds and wants while decoding unique structural elements into designing. The Studio \r\nbrings students, an expertise on professional 3D Modelling techniques that paves way for \r\ndetailed / logical exploration of various structural elements. Since focusing on Industrial \r\nstyle of designing, Steel forms the major material for design explorations along with \r\nother materials. In the Pre - Design Development process, the designer will be exposed to \r\ntechniques of construction with steel and inspiring works of various Industrial Architects. \r\nAftermost, the students will be able to technically approach any given adaptive \r\nreuse projects, considering the available resources; contextual constraints; tangible \r\nand intangible values of the structure to-be renovated. To their level, they could \r\nappreciate and critically review works of any Architects. Besides these, on the aspects \r\nof professionalism, they will also be able to technically produce working drawings with \r\nmaterial specifications.', 1, 0, '2023-01-23', '0000-00-00', 1),
|
||
(5, 1, 'Planning and Organizing Understanding Micro-spaces', 'MCL2005', '5', '230123064913.webp', 'India is home to more than a billion people and keeps adding. The land has become a \r\nprime asset for urban development and housing is a prime necessity for Indians. The \r\narchitecture of micro-spaces encourages user-architect dialogue concerning functionality, \r\nadaptability, and flexibility. Micro Architecture is based on the space-dimensions-functions matrix. Micro Architecture is connected with space confinement and affects the \r\npeople with fewer resources to build houses. Micro Architecture becomes the answer and \r\nhitherto choice for the people with lower incomes working in daily wage occupations and \r\nunorganized sectors. India has 581 million people working in the unorganized sector with \r\nTamil Nadu having more than 7.7 million workers as per eSharm data of the government \r\nof India. \r\nThe studio is focused on providing a learning opportunity to the student to learn about \r\nthe existing informality in the housing sector mainly for the unorganized sector people \r\nsuch as construction workers, tea plantation workers, and migrants working in the \r\napparel industry. The studio is an attempt to reflect on the type of workers’ housing \r\nand assess the space-functions constraints within the purview of flexibility, adaptability, \r\nand innovation. The design of urban housing of mid-to-low rise with low density is \r\naimed to impact students’ knowledge of dealing with the housing industry, associated \r\nchallenges in the design, and practical demand-supply along with paying attention to \r\narchitectural services and universal design principles. The understanding of micro spaces \r\nin architectural design will reorient architecture students towards developing innovative \r\ndesign schemes of residential architecture, which means pushing the creative boundaries \r\nof students.', 1, 1, '2023-01-23', '2023-01-24', 1);
|
||
|
||
-- --------------------------------------------------------
|
||
|
||
--
|
||
-- Table structure for table `subjectdetail`
|
||
--
|
||
|
||
CREATE TABLE `subjectdetail` (
|
||
`id` int(11) NOT NULL,
|
||
`subjectId` int(11) NOT NULL,
|
||
`title` varchar(225) NOT NULL,
|
||
`image` varchar(225) NOT NULL,
|
||
`status` int(11) NOT NULL
|
||
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
|
||
|
||
--
|
||
-- Dumping data for table `subjectdetail`
|
||
--
|
||
|
||
INSERT INTO `subjectdetail` (`id`, `subjectId`, `title`, `image`, `status`) VALUES
|
||
(1, 1, 'Terrain and Architecture', '1.1.jpg', 1),
|
||
(2, 2, 'Planning and Organizing Spatial organization in architecture', '2.2.jpg', 1),
|
||
(3, 3, 'Planning and Organizing The clash of the weathers', '3.3.jpg', 1),
|
||
(4, 4, 'Constructing and Specifying Express it Industrially', '4.4.jpg', 1),
|
||
(5, 5, 'Planning and Organizing Understanding Micro-spaces', '5.5.jpg', 1);
|
||
|
||
--
|
||
-- Indexes for dumped tables
|
||
--
|
||
|
||
--
|
||
-- Indexes for table `degree`
|
||
--
|
||
ALTER TABLE `degree`
|
||
ADD PRIMARY KEY (`id`);
|
||
|
||
--
|
||
-- Indexes for table `department`
|
||
--
|
||
ALTER TABLE `department`
|
||
ADD PRIMARY KEY (`id`);
|
||
|
||
--
|
||
-- Indexes for table `employee`
|
||
--
|
||
ALTER TABLE `employee`
|
||
ADD PRIMARY KEY (`id`);
|
||
|
||
--
|
||
-- Indexes for table `faculty`
|
||
--
|
||
ALTER TABLE `faculty`
|
||
ADD PRIMARY KEY (`id`);
|
||
|
||
--
|
||
-- Indexes for table `project`
|
||
--
|
||
ALTER TABLE `project`
|
||
ADD PRIMARY KEY (`id`);
|
||
|
||
--
|
||
-- Indexes for table `projectdetail`
|
||
--
|
||
ALTER TABLE `projectdetail`
|
||
ADD PRIMARY KEY (`id`);
|
||
|
||
--
|
||
-- Indexes for table `role`
|
||
--
|
||
ALTER TABLE `role`
|
||
ADD PRIMARY KEY (`id`);
|
||
|
||
--
|
||
-- Indexes for table `semester`
|
||
--
|
||
ALTER TABLE `semester`
|
||
ADD PRIMARY KEY (`id`);
|
||
|
||
--
|
||
-- Indexes for table `student`
|
||
--
|
||
ALTER TABLE `student`
|
||
ADD PRIMARY KEY (`id`);
|
||
|
||
--
|
||
-- Indexes for table `subject`
|
||
--
|
||
ALTER TABLE `subject`
|
||
ADD PRIMARY KEY (`id`);
|
||
|
||
--
|
||
-- Indexes for table `subjectdetail`
|
||
--
|
||
ALTER TABLE `subjectdetail`
|
||
ADD PRIMARY KEY (`id`);
|
||
|
||
--
|
||
-- AUTO_INCREMENT for dumped tables
|
||
--
|
||
|
||
--
|
||
-- AUTO_INCREMENT for table `degree`
|
||
--
|
||
ALTER TABLE `degree`
|
||
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
|
||
|
||
--
|
||
-- AUTO_INCREMENT for table `department`
|
||
--
|
||
ALTER TABLE `department`
|
||
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
|
||
|
||
--
|
||
-- AUTO_INCREMENT for table `employee`
|
||
--
|
||
ALTER TABLE `employee`
|
||
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
|
||
|
||
--
|
||
-- AUTO_INCREMENT for table `faculty`
|
||
--
|
||
ALTER TABLE `faculty`
|
||
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6;
|
||
|
||
--
|
||
-- AUTO_INCREMENT for table `project`
|
||
--
|
||
ALTER TABLE `project`
|
||
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
|
||
|
||
--
|
||
-- AUTO_INCREMENT for table `projectdetail`
|
||
--
|
||
ALTER TABLE `projectdetail`
|
||
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;
|
||
|
||
--
|
||
-- AUTO_INCREMENT for table `role`
|
||
--
|
||
ALTER TABLE `role`
|
||
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
|
||
|
||
--
|
||
-- AUTO_INCREMENT for table `semester`
|
||
--
|
||
ALTER TABLE `semester`
|
||
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;
|
||
|
||
--
|
||
-- AUTO_INCREMENT for table `student`
|
||
--
|
||
ALTER TABLE `student`
|
||
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
|
||
|
||
--
|
||
-- AUTO_INCREMENT for table `subject`
|
||
--
|
||
ALTER TABLE `subject`
|
||
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6;
|
||
|
||
--
|
||
-- AUTO_INCREMENT for table `subjectdetail`
|
||
--
|
||
ALTER TABLE `subjectdetail`
|
||
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=8;
|
||
COMMIT;
|
||
|
||
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
|
||
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
|
||
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
|