HTML and CSS Reference
In-Depth Information
The relation type between
BOOK
Entity and
BOOK_REQUEST
is
"one-to-many"
, which means that a book can have 0
or more book requests.
2.
BOOK_REQUEST Entity
:
BOOK_REQUEST
entity is responsible for storing the requests for the
book that are performed by the application users. It has the attributes shown in Table
13-2
.
Table 13-2.
BOOK_REQUEST table
Attribute name
Logical Type
Nullable
Description
ID
Integer
Primary Key (NOT NULL)
Auto-generated ID that represents request ID
BOOK_ID
Integer
NOT NULL
Foreign key that represents the topic ID
USER_ID
String(64)
NOT NULL
Foreign key that represents the user ID
REQUEST_TIME
Long
NULLABLE
Request time
RESPONSE_TIME
Long
NULLABLE
Response time
STAT U S
Integer
NOT NULL
The request status. It has one of three values:
1, which represents pending status
2, which represents rejected status
3, which represents approved status
3.
USER Entity
:
USER
entity is responsible for storing the Mega App users. It has the
following attributes as shown in Table
13-3
.
Table 13-3.
MEGA_USER Entity
Attribute name
Logical Type
Nullable
Description
ID
String(64)
Primary Key (NOT NULL)
The user login name
FIRST_NAME
String(32)
NOT NULL
The user first name
LAST_NAME
String(32)
NOT NULL
The user last name
PASSWORD
String(32)
NOT NULL
The user password
The relation type between
USER
Entity and
BOOK_REQUEST
is
"one-to-many"
, which means that a user can perform
0 or more book requests.
The relation type between
USER
Entity and
USER_GROUP
is
"one-to-many"
, which means that a user can be in 0 or
more groups.
■
Note
the Mega app code ensures that the user will be always a member in one group.
4.
USER_GROUP Entity
:
USER_GROUP
entity is responsible for storing the Mega App user
groups. It has the attributes shown in Table
13-4
.
