Uploading All Files

Author: SuwaidAslam

ELearningSystem.sql

@@ -0,0 +1,101 @@
+-- Database Name = 'ELearningSystem'
+
+Create Database ELearningSystem;
+
+use ELearningSystem;
+
+SET GLOBAL max_allowed_packet = 1024*1024*14;
+
+create Table Admin(
+Adminid int Not Null AUTO_INCREMENT,
+fname varchar(150) Not Null,
+lname varchar(150),
+Email_ID varchar(250),
+username varchar(20) Not Null Unique,
+password varchar(20),
+Gender varchar(10),
+picture MEDIUMBLOB,
+Primary Key (Adminid)
+) ENGINE = InnoDB DEFAULT CHARSET = latin1;
+
+Insert Into Admin (fname, lname, Email_ID, username, password, Gender)
+Values('Suwaid', 'Aslam', '[email protected]', 'admin', 'admin', 'Male');
+
+
+create Table Student(
+stdID int Not Null AUTO_INCREMENT,
+fname varchar(150) Not Null,
+lname varchar(150),
+Email_ID varchar(250),
+username varchar(20) Not Null Unique,
+password varchar(20),
+Gender varchar(10),
+Registration_Date Date Not Null,
+Last_Login Datetime,
+picture MEDIUMBLOB,
+Primary Key (stdID)
+) ENGINE = InnoDB DEFAULT CHARSET = latin1;
+
+
+create Table Teacher(
+teacherID int Not Null AUTO_INCREMENT,
+fname varchar(150) Not Null,
+lname varchar(150),
+Email_ID varchar(250),
+username varchar(20) Not Null Unique,
+password varchar(20),
+Gender varchar(10),
+Registration_Date Date Not Null,
+Last_Login Datetime,
+picture MEDIUMBLOB,
+Primary Key (teacherID)
+) ENGINE = InnoDB DEFAULT CHARSET = latin1;
+
+
+create Table Subjects(
+Subject_ID int Not Null AUTO_INCREMENT,
+Name varchar(150) Not Null Unique,
+Primary Key (Subject_ID),
+Adminid int Not Null,
+CONSTRAINT Adminid_fk Foreign Key (Adminid) References Admin(Adminid) ON DELETE CASCADE
+) ENGINE = InnoDB DEFAULT CHARSET = latin1;
+
+create Table Courses(
+course_ID int Not Null AUTO_INCREMENT,
+Name varchar(250) Not Null Unique,
+Description varchar(1000) Not Null,
+Content varchar(3000) Not Null,
+teacherID int Not Null,
+Subject_ID int Not Null,
+Primary Key(course_ID),
+CONSTRAINT teacherID_fk Foreign Key (teacherID) References Teacher(teacherID) ON DELETE CASCADE,
+CONSTRAINT subjectID_fk Foreign Key (Subject_ID) References Subjects(Subject_ID) ON DELETE CASCADE
+) ENGINE = InnoDB DEFAULT CHARSET = latin1;
+
+create Table Enrollments(
+Enrollment_ID int Not Null AUTO_INCREMENT,
+Enrollment_Date Date Not Null,
+course_ID int Not Null,
+stdID int Not Null,
+CONSTRAINT courseID_fk Foreign Key (course_ID) References Courses(course_ID) ON DELETE CASCADE,
+CONSTRAINT stdID_fk Foreign Key (stdID) References Student(stdID) ON DELETE CASCADE,
+Primary Key(Enrollment_ID),
+UNIQUE KEY unique_Enrollment(course_ID, stdID)
+) ENGINE = InnoDB DEFAULT CHARSET = latin1;
+
+
+create Table Messages(
+Message_ID int Not Null AUTO_INCREMENT,
+message varchar(2000) Not Null,
+time_Stamp Datetime Not Null,
+User_ID int Not Null,
+toUser_ID int Not Null,
+Primary Key (Message_ID)
+) ENGINE = InnoDB DEFAULT CHARSET = latin1;
+
+create Table MessageUsers(
+User_ID int Not Null,
+Message_ID int Not Null,
+CONSTRAINT message_ID_fk Foreign Key (Message_ID) References Messages(Message_ID) ON DELETE CASCADE
+) ENGINE = InnoDB DEFAULT CHARSET = latin1;
+

build.xml

@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- You may freely edit this file. See commented blocks below for -->
+<!-- some examples of how to customize the build. -->
+<!-- (If you delete it and reopen the project it will be recreated.) -->
+<!-- By default, only the Clean and Build commands use this build script. -->
+<!-- Commands such as Run, Debug, and Test only use this build script if -->
+<!-- the Compile on Save feature is turned off for the project. -->
+<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
+<!-- in the project's Project Properties dialog box.-->
+<project name="JavaSemesterProject" default="default" basedir=".">
+    <description>Builds, tests, and runs the project JavaSemesterProject.</description>
+    <import file="nbproject/build-impl.xml"/>
+    <!--
+
+    There exist several targets which are by default empty and which can be 
+    used for execution of your tasks. These targets are usually executed 
+    before and after some main targets. They are: 
+
+      -pre-init:                 called before initialization of project properties
+      -post-init:                called after initialization of project properties
+      -pre-compile:              called before javac compilation
+      -post-compile:             called after javac compilation
+      -pre-compile-single:       called before javac compilation of single file
+      -post-compile-single:      called after javac compilation of single file
+      -pre-compile-test:         called before javac compilation of JUnit tests
+      -post-compile-test:        called after javac compilation of JUnit tests
+      -pre-compile-test-single:  called before javac compilation of single JUnit test
+      -post-compile-test-single: called after javac compilation of single JUunit test
+      -pre-jar:                  called before JAR building
+      -post-jar:                 called after JAR building
+      -post-clean:               called after cleaning build products
+
+    (Targets beginning with '-' are not intended to be called on their own.)
+
+    Example of inserting an obfuscator after compilation could look like this:
+
+        <target name="-post-compile">
+            <obfuscate>
+                <fileset dir="${build.classes.dir}"/>
+            </obfuscate>
+        </target>
+
+    For list of available properties check the imported 
+    nbproject/build-impl.xml file. 
+
+
+    Another way to customize the build is by overriding existing main targets.
+    The targets of interest are: 
+
+      -init-macrodef-javac:     defines macro for javac compilation
+      -init-macrodef-junit:     defines macro for junit execution
+      -init-macrodef-debug:     defines macro for class debugging
+      -init-macrodef-java:      defines macro for class execution
+      -do-jar:                  JAR building
+      run:                      execution of project 
+      -javadoc-build:           Javadoc generation
+      test-report:              JUnit report generation
+
+    An example of overriding the target for project execution could look like this:
+
+        <target name="run" depends="JavaSemesterProject-impl.jar">
+            <exec dir="bin" executable="launcher.exe">
+                <arg file="${dist.jar}"/>
+            </exec>
+        </target>
+
+    Notice that the overridden target depends on the jar target and not only on 
+    the compile target as the regular run target does. Again, for a list of available 
+    properties which you can use, check the target you are overriding in the
+    nbproject/build-impl.xml file. 
+
+    -->
+</project>

build/built-jar.properties

@@ -0,0 +1,4 @@
+#Sun, 26 Dec 2021 23:00:45 +0500
+
+
+C\:\\Users\\Suwaid\\Desktop\\JavaSemesterProject=