Comments regarding 1.0 version
Comments regarding 1.0 version

Line 15 - Should we change the length of NUMBER from 16 to 10, in accordance to the number of digits of a standard mobile number?
Line 25 - For the email address, we could also have underscores, full-stops and hyphens as part of the email address.
                So shall we change the code to: [a-zA-Z0-9_\-\.]+@...?
Line 42 - If BookingID is already a part of a composite primary key, do we still need to set the domain constraint as UNIQUE?
Line 48 - I am not sure why TableID should be included in the 'Booking' table. Since 'Booking' and 'Table' is a many to many relationship,
                I don't think either of the tables take on the primary key of the other as the foreign key. Rather, we should create a new relation
                table called 'Reserves' that takes the primary keys of both the tables in relation as its composite primary key and foreign key. 
Line 52 - Similarly, I don't think this constraint should exist as part of this table.
Line 74 - Price can also be in decimal points (up to 2 dp), so we may need to change NUMBER(8) to NUMBER(8,2).
wx-Yao/Didactic-DBMS,wx-Yao/Didactic-DBMS,wx-Yao/Didactic-DBMS,wx-Yao/Didactic-DBMS,wx-Yao/Didactic-DBMS