I want to create a database with 3 main entities each of which will be subtyped further(by subtype I mean generalization-specialization). This database will support a website where the users can ONLY Read the database. I don’t know how many users will hit the website daily. As I see vision it, the database will have […]
Categories
Designing an (almost) Read only database
- Post author By Jessica Alba
- Post date May 22, 2020
- No Comments on Designing an (almost) Read only database
- Tags "Insider"), "Outsider"); Insiders are further classified into ONE out of 3 categories - Team-mate(s), 000 rows. Once a week I would like to update the database with around 10 records in ALL in various entities. Should I use InndoDB? What opt, 2, Alumni and Advisor(s) This is NOT a Gen-Spec pattern since ALL 3 categories have the SAME variables. CREATE TABLE Insider_Person_Category (i, category CHAR(10) NOT NULL, category CHAR(10)) ENGINE=InnoDB DEFAULT CHARSET=utf8; INSERT INTO Person_Category(id, category) VALUES (1, CONSTRAINT Insider_Person_Category_PK PRIMARY KEY (id)) ENGINE=InnoDB DEFAULT CHARSET=utf8; INSERT INTO Insider_Person_Category (id, for the sake of a simple example I have used ONE entity Person which has subtypes. DROP DATABASE IF EXISTS People_Database; CREATE DATABASE, I want to create a database with 3 main entities each of which will be subtyped further(by subtype I mean generalization-specialization). Th, since each of the 2 categories have some variables in common and some specific variables. By Gen-Spec I mean Generalization-Specialization., the database will have a TOTAL of 500