This information comes straight from my life. I was forced to learn how
- Bugzilla organizes database because of nitpicky requests from users for tiny
- changes in wording, rather than having people re-educate themselves or
- figure out how to work our procedures around the tool. It sucks, but it can
- and will happen to you, so learn how the schema works and deal with it when it
- comes.
-
This information comes straight from my life. I was forced to learn
+ how Bugzilla organizes database because of nitpicky requests from users
+ for tiny changes in wording, rather than having people re-educate
+ themselves or figure out how to work our procedures around the tool. It
+ sucks, but it can and will happen to you, so learn how the schema works
+ and deal with it when it comes.
So, here you are with your brand-new installation of Bugzilla. You've got
- MySQL set up, Apache working right, Perl DBI and DBD talking to the database
- flawlessly. Maybe you've even entered a few test bugs to make sure email's
- working; people seem to be notified of new bugs and changes, and you can
- enter and edit bugs to your heart's content. Perhaps you've gone through the
- trouble of setting up a gateway for people to submit bugs to your database via
- email, have had a few people test it, and received rave reviews from your beta
- testers.
-
So, here you are with your brand-new installation of Bugzilla.
+ You've got MySQL set up, Apache working right, Perl DBI and DBD talking
+ to the database flawlessly. Maybe you've even entered a few test bugs to
+ make sure email's working; people seem to be notified of new bugs and
+ changes, and you can enter and edit bugs to your heart's content. Perhaps
+ you've gone through the trouble of setting up a gateway for people to
+ submit bugs to your database via email, have had a few people test it,
+ and received rave reviews from your beta testers.
What's the next thing you do? Outline a training strategy for your
- development team, of course, and bring them up to speed on the new tool you've
- labored over for hours.
-
What's the next thing you do? Outline a training strategy for your
+ development team, of course, and bring them up to speed on the new tool
+ you've labored over for hours.
Your first training session starts off very well! You have a captive
- audience which seems enraptured by the efficiency embodied in this thing called
- "Bugzilla". You are caught up describing the nifty features, how people can
- save favorite queries in the database, set them up as headers and footers on
- their pages, customize their layouts, generate reports, track status with
- greater efficiency than ever before, leap tall buildings with a single bound
- and rescue Jane from the clutches of Certain Death!
-
Your first training session starts off very well! You have a
+ captive audience which seems enraptured by the efficiency embodied in
+ this thing called "Bugzilla". You are caught up describing the nifty
+ features, how people can save favorite queries in the database, set them
+ up as headers and footers on their pages, customize their layouts,
+ generate reports, track status with greater efficiency than ever before,
+ leap tall buildings with a single bound and rescue Jane from the clutches
+ of Certain Death!
But Certain Death speaks up -- a tiny voice, from the dark corners of the
- conference room. "I have a concern," the voice hisses from the darkness,
- "about the use of the word 'verified'.
-
But Certain Death speaks up -- a tiny voice, from the dark corners
+ of the conference room. "I have a concern," the voice hisses from the
+ darkness, "about the use of the word 'verified'.
The room, previously filled with happy chatter, lapses into reverential
- silence as Certain Death (better known as the Vice President of Software
- Engineering) continues. "You see, for two years we've used the word 'verified'
- to indicate that a developer or quality assurance engineer has confirmed that,
- in fact, a bug is valid. I don't want to lose two years of training to a
- new software product. You need to change the bug status of 'verified' to
- 'approved' as soon as possible. To avoid confusion, of course."
-
The room, previously filled with happy chatter, lapses into
+ reverential silence as Certain Death (better known as the Vice President
+ of Software Engineering) continues. "You see, for two years we've used
+ the word 'verified' to indicate that a developer or quality assurance
+ engineer has confirmed that, in fact, a bug is valid. I don't want to
+ lose two years of training to a new software product. You need to change
+ the bug status of 'verified' to 'approved' as soon as possible. To avoid
+ confusion, of course."
Oh no! Terror strikes your heart, as you find yourself mumbling "yes, yes, I
- don't think that would be a problem," You review the changes with Certain
- Death, and continue to jabber on, "no, it's not too big a change. I mean, we
- have the source code, right? You know, 'Use the Source, Luke' and all that...
- no problem," All the while you quiver inside like a beached jellyfish bubbling,
- burbling, and boiling on a hot Jamaican sand dune...
-
Oh no! Terror strikes your heart, as you find yourself mumbling
+ "yes, yes, I don't think that would be a problem," You review the changes
+ with Certain Death, and continue to jabber on, "no, it's not too big a
+ change. I mean, we have the source code, right? You know, 'Use the
+ Source, Luke' and all that... no problem," All the while you quiver
+ inside like a beached jellyfish bubbling, burbling, and boiling on a hot
+ Jamaican sand dune...
Thus begins your adventure into the heart of Bugzilla. You've been forced
- to learn about non-portable enum() fields, varchar columns, and tinyint
- definitions. The Adventure Awaits You!
-
Thus begins your adventure into the heart of Bugzilla. You've been
+ forced to learn about non-portable enum() fields, varchar columns, and
+ tinyint definitions. The Adventure Awaits You!
If you were like me, at this point you're totally clueless
- about the internals of MySQL, and if it weren't for this
- executive order from the Vice President you couldn't care less
- about the difference between a If you were like me, at this point you're totally clueless about
+ the internals of MySQL, and if it weren't for this executive order from
+ the Vice President you couldn't care less about the difference between
+ a
+ "bigint" and a
-
+
+ and a
+ "tinyint" entry in MySQL. I recommend you refer
- to the MySQL documentation, available at
+
+ entry in MySQL. I recommend you refer to the MySQL documentation,
+ available at
+ MySQL.com. Below are the basics you need to know about the Bugzilla database. Check the chart above for more details.
-
+
+ . Below are the basics you need to know about the Bugzilla database.
+ Check the chart above for more details.
To connect to your database:
-
To connect to your database:
bash#
+
+ mysql
+
+ -u root
-
If this works without asking you for a password,
- If this works without asking you for a password,
+ shame on you! You should have
- locked your security down like the installation
- instructions told you to. You can find details on
- locking down your database in the Bugzilla FAQ in this
- directory (under "Security"), or more robust security
- generalities in the MySQL searchable documentation at
- http://www.mysql.com/php/manual.php3?section=Privilege_system .
-
+
+ ! You should have locked your security down like the installation
+ instructions told you to. You can find details on locking down
+ your database in the Bugzilla FAQ in this directory (under
+ "Security"), or more robust security generalities in the
+ MySQL
+ searchable documentation.
+
You should now be at a prompt that looks like
- this:
You should now be at a prompt that looks like this:
mysql>
+
At the prompt, if At the prompt, if
+ "bugs" is the name
- you chose in the
+
+ is the name you chose in the
+ localconfig file
- for your Bugzilla database, type:
+
+ file for your Bugzilla database, type:
mysql
+
+ use bugs;
Don't forget the ";" at the end of
- each line, or you'll be kicking yourself later.
Imagine your MySQL database as a series of
- spreadsheets, and you won't be too far off. If you use this
- command:
Imagine your MySQL database as a series of spreadsheets, and
+ you won't be too far off. If you use this command:
mysql>
+ show tables from bugs;
+
you'll be able to see all the
- you'll be able to see the names of all the
+ "spreadsheets" (tables) in your database. It
- is similar to a file system, only faster and more robust for
- certain types of operations.
+ (tables) in your database.
From the command issued above, ou should have some
output that looks like this:
-
+
-
Here's an overview of what each table does. Most columns in each table have
descriptive names that make it fairly trivial to figure out their jobs.
@@ -490,21 +478,6 @@ Although you can query by the enum field,&nbs
of "APPROVED" until you make the perl changes. Note that this change I
mentioned can also be done by editing checksetup.pl, which automates a lot of
this. But you need to know this stuff anyway, right?
-
- I hope this database tutorial has been useful for you. If you have comments
-to add, questions, concerns, etc. please direct them to
-mbarnson@excitehome.net. Please direct flames to /dev/null :) Have a nice
-day!
-
-
-
-===
-LINKS
-===
-
-Great MySQL tutorial site:
-http://www.devshed.com/Server_Side/MySQL/
-
NextMySQL Permissions & Grant TablesUseful Patches and Utilities for Bugzilla