Article Preview
Buy Now
| Print: | |
| PDF: |
From Scratch
Swatter
A simple bug database
Issue: 6.2 (January/February 2008)
Author: Brad Rhine
Article Description: No description available.
Article Length (in bytes): 7,862
Starting Page Number: 34
RBD Number: 6214
Resource File(s): None
Related Link(s): None
Known Limitations: None
Excerpt of article text...
In this issue, we begin a new project. We recently completed iDater, a small program to edit files' creation and modification dates. Today, we begin Swatter, a simple bug database.
Be forewarned: we're not going to get into any REALbasic code in this issue. Instead, we're going to discuss what our program should do and how we should set up the database (so we will look at some SQL code).
Defining The Goal
Since Swatter is significantly more complicated than iDater, the very first thing we need to do is determine our requirements. What does a bug database need to do? Well, first it needs to keep track of our projects and their associated metadata. If you really wanted to keep it simple, you could limit the program to one project, but that's a needless limitation, especially when dealing with an API as easy to use as the REALbasic database API. In addition to our projects, Swatter needs to keep track of bugs and feature requests, which we'll combine and refer to as issues. We need to make sure that each issue is tied to a project. We also need to be able to edit and delete issues requests as necessary. In addition, we should build a way to track our users who report issues. Each user could be related to any number of issues.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.
|
