Determining the App’s Functionality and Structure - Realtime Web Apps: With HTML5 WebSocket, PHP, and jQuery - page 75

Determining the Tables and Structure
With normalization in mind, let's define the tables for your app. To recap, the data that you need to store is the
following:

• The room's name

• A unique identifier for the room

• Whether or not the room is active

• The presenter's name

• A unique identifier for the presenter

• The presenter's email

• The question

• A unique identifier for the question

• Whether or not the question is answered

• The number of votes for the question

If you group this data normally, you should end up with four tables:

• Presenters

• Rooms

• Questions

• Votes

Presenters Table
The first table, presenters , stores the presenter's name, email, and a unique ID (see Table 5-7 ).

Table 5-7. presenters Table

id name email

Rooms Table
The rooms table will store a room's unique ID, its name, and whether or not it's active (see Table 5-8 ).

Table 5-8. rooms Table

id name is_active