(I hate untangling the mess others create)

This commit is contained in:
2023-11-13 14:11:33 +02:00
parent 4273631d5d
commit 8589ce2817
8 changed files with 66 additions and 59 deletions

1
.gitignore vendored
View File

@@ -35,3 +35,4 @@ google-services.json
# Android Profiling
*.hprof
/Figma_UI/

15
MyApp_1/.gitignore vendored
View File

@@ -1,15 +0,0 @@
*.iml
.gradle
/local.properties
/.idea/caches
/.idea/libraries
/.idea/modules.xml
/.idea/workspace.xml
/.idea/navEditor.xml
/.idea/assetWizardSettings.xml
.DS_Store
/build
/captures
.externalNativeBuild
.cxx
local.properties

3
MyApp_1/.idea/.gitignore generated vendored
View File

@@ -1,3 +0,0 @@
# Default ignored files
/shelf/
/workspace.xml

View File

@@ -1,6 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
<component name="CompilerConfiguration">
<bytecodeTargetLevel target="17" />
</component>
</project>

View File

@@ -1,19 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
<component name="GradleSettings">
<option name="linkedExternalProjectsSettings">
<GradleProjectSettings>
<option name="testRunner" value="GRADLE" />
<option name="distributionType" value="DEFAULT_WRAPPED" />
<option name="externalProjectPath" value="$PROJECT_DIR$" />
<option name="gradleJvm" value="jbr-17" />
<option name="modules">
<set>
<option value="$PROJECT_DIR$" />
<option value="$PROJECT_DIR$/app" />
</set>
</option>
</GradleProjectSettings>
</option>
</component>
</project>

10
MyApp_1/.idea/misc.xml generated
View File

@@ -1,10 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
<component name="ExternalStorageConfigurationManager" enabled="true" />
<component name="ProjectRootManager" version="2" languageLevel="JDK_17" default="true" project-jdk-name="jbr-17" project-jdk-type="JavaSDK">
<output url="file://$PROJECT_DIR$/build/classes" />
</component>
<component name="ProjectType">
<option name="id" value="Android" />
</component>
</project>

6
MyApp_1/.idea/vcs.xml generated
View File

@@ -1,6 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
<component name="VcsDirectoryMappings">
<mapping directory="$PROJECT_DIR$/.." vcs="Git" />
</component>
</project>

65
db_related/serber_sql.sql Normal file
View File

@@ -0,0 +1,65 @@
-- Table for Users
-- U_ID => User ID, Primary Key
-- first_name => User's First Name
-- last_name => User's Last Name
-- U_email => User's Registered Email
-- U_password => User's Password
CREATE TABLE users(U_ID SERIAL PRIMARY KEY,
first_name varchar(255) NOT NULL,
last_name varchar(255) NOT NULL,
U_email varchar(255) NOT NULL UNIQUE,
U_password varchar(255) NOT NULL
);
-- Table for Stations
-- S_ID => Station ID in fashion of: 3xx denotes taking both lines 1 and 2,
-- 2xx denotes taking Line 2 Only,
-- 1xx denotes taking Line 1 Only.
-- name_ar => Station's name in Arabic
-- name_en => Station's name in English
-- tram_lines (DEPRICATE FROM ERD) => Would've denoted which lines are allowed
-- geo_loc => Geographical Location (Latitude, Longitude)
-- Comment regarding the "GEOGRAPHY" data type
-- https://stackoverflow.com/questions/30322924/how-to-store-longitude-latitude-as-a-geography-in-sql-server-2014
-- Double check for later purposes
CREATE TABLE stations(S_ID SERIAL PRIMARY KEY,
name_ar varchar(255) NOT NULL,
name_en varchar(255) NOT NULL,
-- Debating whether or not to denote
-- Tram lines as 1, 2, or 3
-- instead of multiple values
location GEOGRAPHY
);
-- Forgot Relation between User and Station
-- "Preferred Stations", need to rework ERD
-- Anyhow, Insert a new table as relation
-- M:N (i.e. Separate Table)
-- Where U_ID + S_ID (User ID, Station ID)
-- are compound keys
CREATE TABLE prefers(pref_UID SERIAL,
pref_SID SERIAL,
CONSTRAINT fk1 FOREIGN KEY (pref_UID) REFERENCES users(U_ID),
CONSTRAINT fk2 FOREIGN KEY (pref_SID) REFERENCES stations(S_ID),
CONSTRAINT pk1 PRIMARY KEY (pref_UID, pref_SID)
);
-- Ought to create table for "Arrival"
-- Except I dond see how it'd be implemented properly
-- but do take a look at whatever the mcfuck i write below
-- Documenting the Table
-- time_of_day => Time object, nanosecond accuracy, y'all handle it idk
-- week_day => varchar as {Mon, Tue, Wed}, Could probs just encode with 0 -> 6
-- tram_line => int ranging 1 -> 4
-- fill_status => Boolean, 1 full, 0 not as full
CREATE TABLE arrival(time_of_day TIME,
week_day INTEGER,
tram_line INTEGER,
fill_status BOOLEAN
CONSTRAINT ck PRIMARY KEY (week_day,tram_line)
CONSTRAINT in_week CHECK (week_day >= 0 AND week_day <= 6)
CONSTRAINT valid_line CHECK (tram_line >= 1 AND tram_line <= 4)
);