Rob Allen, Nick Lo, and Steven Brown
"Zend Framework in Action"
Licensed to Menshu You
Zend Framework in Action (Ch010) Manning Publications Co. 6
9.3.1 Designing the application
After a brainstorming session we decide that our support tracker has the following requirements:
1. Simple enough that we??™ll want to use it rather than just email.
2. Update-able, e.g. changing the status of a bug.
3. Integrates with current user data. No new usernames and passwords.
4. Notification by email to all concerned.
5. Ability to add attachments, e.g. screenshots, and have them sent with notification emails.
6. Formatted emails for quick scanning.
The second requirement makes it clear that we are going to need to store this data and figure 9.2 shows the
initial table structure of our application. Since we will have many support issues to a user this is reflected in
the one-to-many relationship of the schema.
Figure 9.2 The initial database structure of our support tracker requiring the addition of a single ???support??? table alongside our
existing ???users??? table
If you??™ve read chapter 5 you should already be familiar with the use of Zend_Db_Table relationships and
recognise the model that follows in listing 9.4. By specifying the $_dependentTables and $_referenceMap we
are defining the relationship between the existing Users class from our Places application and our new Support
class.
Pages:
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255