BugsSite/docs/html/dbdoc.html - WebKit - Git at Google

 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML
 ><HEAD
 ><TITLE
 >MySQL Bugzilla Database Introduction</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.20.1
     Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="Customising Bugzilla"
 HREF="customization.html"><LINK
 REL="PREVIOUS"
 TITLE="Modifying Your Running System"
 HREF="dbmodify.html"><LINK
 REL="NEXT"
 TITLE="Integrating Bugzilla with Third-Party Tools"
 HREF="integration.html"></HEAD
 ><BODY
 CLASS="section"
 BGCOLOR="#FFFFFF"
 TEXT="#000000"
 LINK="#0000FF"
 VLINK="#840084"
 ALINK="#0000FF"
 ><DIV
 CLASS="NAVHEADER"
 ><TABLE
 SUMMARY="Header navigation table"
 WIDTH="100%"
 BORDER="0"
 CELLPADDING="0"
 CELLSPACING="0"
 ><TR
 ><TH
 COLSPAN="3"
 ALIGN="center"
 >The Bugzilla Guide - 2.20.1
     Release</TH
 ></TR
 ><TR
 ><TD
 WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
 HREF="dbmodify.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
 ><TD
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
 >Chapter 5. Customising Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
 HREF="integration.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
 ></TR
 ></TABLE
 ><HR
 ALIGN="LEFT"
 WIDTH="100%"></DIV
 ><DIV
 CLASS="section"
 ><H1
 CLASS="section"
 ><A
 NAME="dbdoc"
 >5.5. MySQL Bugzilla Database Introduction</A
 ></H1
 ><P
 >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.</P
 ><P
 >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.</P
 ><P
 >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.</P
 ><P
 >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!</P
 ><P
 >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'."</P
 ><P
 >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."</P
 ><P
 >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...</P
 ><P
 >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!</P
 ><DIV
 CLASS="section"
 ><H2
 CLASS="section"
 ><A
 NAME="AEN2062"
 >5.5.1. Bugzilla Database Basics</A
 ></H2
 ><P
 >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
       <SPAN
 CLASS="QUOTE"
 >"bigint"</SPAN
 >

       and a
       <SPAN
 CLASS="QUOTE"
 >"tinyint"</SPAN
 >

       entry in MySQL. I recommend you refer to the
       <A
 HREF="http://www.mysql.com/documentation/"
 TARGET="_top"
 >MySQL documentation</A
 >
       . Below are the basics you need to know about the Bugzilla database.
       Check the chart above for more details.</P
 ><P
 >&#13;        <P
 ></P
 ><OL
 TYPE="1"
 ><LI
 ><P
 >To connect to your database:</P
 ><P
 >&#13;              <SAMP
 CLASS="prompt"
 >bash#</SAMP
 >

               <B
 CLASS="command"
 >mysql</B
 >

               <VAR
 CLASS="parameter"
 >-u root</VAR
 >
             </P
 ><P
 >If this works without asking you for a password,
             <EM
 >shame on you</EM
 >

             ! 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
             <A
 HREF="http://www.mysql.com/php/manual.php3?section=Privilege_system"
 TARGET="_top"
 >MySQL
             searchable documentation</A
 >.
             </P
 ></LI
 ><LI
 ><P
 >You should now be at a prompt that looks like this:</P
 ><P
 >&#13;              <SAMP
 CLASS="prompt"
 >mysql&#62;</SAMP
 >
             </P
 ><P
 >At the prompt, if
             <SPAN
 CLASS="QUOTE"
 >"bugs"</SPAN
 >

             is the name you chose in the
             <TT
 CLASS="filename"
 >localconfig</TT
 >

             file for your Bugzilla database, type:</P
 ><P
 >&#13;              <SAMP
 CLASS="prompt"
 >mysql</SAMP
 >

               <B
 CLASS="command"
 >use bugs;</B
 >
             </P
 ></LI
 ></OL
 >
       </P
 ><DIV
 CLASS="section"
 ><H3
 CLASS="section"
 ><A
 NAME="AEN2089"
 >5.5.1.1. Bugzilla Database Tables</A
 ></H3
 ><P
 >Imagine your MySQL database as a series of spreadsheets, and
         you won't be too far off. If you use this command:</P
 ><P
 >&#13;          <SAMP
 CLASS="prompt"
 >mysql&#62;</SAMP
 >
           <B
 CLASS="command"
 >show tables from bugs;</B
 >
         </P
 ><P
 >you'll be able to see the names of all the
         <SPAN
 CLASS="QUOTE"
 >"spreadsheets"</SPAN
 >
         (tables) in your database.</P
 ><P
 >From the command issued above, ou should have some
 	  output that looks like this:
 <TABLE
 BORDER="0"
 BGCOLOR="#E0E0E0"
 WIDTH="100%"
 ><TR
 ><TD
 ><FONT
 COLOR="#000000"
 ><PRE
 CLASS="programlisting"
 >&#13;+-------------------+
 | Tables in bugs    |
 +-------------------+
 | attachments       |
 | bugs              |
 | bugs_activity     |
 | cc                |
 | components        |
 | dependencies      |
 | fielddefs         |
 | groups            |
 | keyworddefs       |
 | keywords          |
 | logincookies      |
 | longdescs         |
 | milestones        |
 | namedqueries      |
 | products          |
 | profiles          |
 | profiles_activity |
 | tokens            |
 | versions          |
 | votes             |
 | watch             |
 +-------------------+
 </PRE
 ></FONT
 ></TD
 ></TR
 ></TABLE
 >
 </P
 ><P
 CLASS="literallayout"
 ><br>
 &nbsp;&nbsp;Here's&nbsp;an&nbsp;overview&nbsp;of&nbsp;what&nbsp;each&nbsp;table&nbsp;does.&nbsp;Most&nbsp;columns&nbsp;in&nbsp;each&nbsp;table&nbsp;have<br>
 descriptive&nbsp;names&nbsp;that&nbsp;make&nbsp;it&nbsp;fairly&nbsp;trivial&nbsp;to&nbsp;figure&nbsp;out&nbsp;their&nbsp;jobs.<br>
 <br>
 attachments:&nbsp;This&nbsp;table&nbsp;stores&nbsp;all&nbsp;attachments&nbsp;to&nbsp;bugs.&nbsp;It&nbsp;tends&nbsp;to&nbsp;be&nbsp;your<br>
 largest&nbsp;table,&nbsp;yet&nbsp;also&nbsp;generally&nbsp;has&nbsp;the&nbsp;fewest&nbsp;entries&nbsp;because&nbsp;file<br>
 attachments&nbsp;are&nbsp;so&nbsp;(relatively)&nbsp;large.<br>
 <br>
 bugs:&nbsp;&nbsp;This&nbsp;is&nbsp;the&nbsp;core&nbsp;of&nbsp;your&nbsp;system.&nbsp;The&nbsp;bugs&nbsp;table&nbsp;stores&nbsp;most&nbsp;of&nbsp;the<br>
 current&nbsp;information&nbsp;about&nbsp;a&nbsp;bug,&nbsp;with&nbsp;the&nbsp;exception&nbsp;of&nbsp;the&nbsp;info&nbsp;stored&nbsp;in&nbsp;the<br>
 other&nbsp;tables.<br>
 <br>
 bugs_activity:&nbsp;&nbsp;This&nbsp;stores&nbsp;information&nbsp;regarding&nbsp;what&nbsp;changes&nbsp;are&nbsp;made&nbsp;to&nbsp;bugs<br>
 when&nbsp;--&nbsp;a&nbsp;history&nbsp;file.<br>
 <br>
 cc:&nbsp;&nbsp;This&nbsp;tiny&nbsp;table&nbsp;simply&nbsp;stores&nbsp;all&nbsp;the&nbsp;CC&nbsp;information&nbsp;for&nbsp;any&nbsp;bug&nbsp;which&nbsp;has<br>
 any&nbsp;entries&nbsp;in&nbsp;the&nbsp;CC&nbsp;field&nbsp;of&nbsp;the&nbsp;bug.&nbsp;Note&nbsp;that,&nbsp;like&nbsp;most&nbsp;other&nbsp;tables&nbsp;in<br>
 Bugzilla,&nbsp;it&nbsp;does&nbsp;not&nbsp;refer&nbsp;to&nbsp;users&nbsp;by&nbsp;their&nbsp;user&nbsp;names,&nbsp;but&nbsp;by&nbsp;their&nbsp;unique<br>
 userid,&nbsp;stored&nbsp;as&nbsp;a&nbsp;primary&nbsp;key&nbsp;in&nbsp;the&nbsp;profiles&nbsp;table.<br>
 <br>
 components:&nbsp;This&nbsp;stores&nbsp;the&nbsp;programs&nbsp;and&nbsp;components&nbsp;(or&nbsp;products&nbsp;and<br>
 components,&nbsp;in&nbsp;newer&nbsp;Bugzilla&nbsp;parlance)&nbsp;for&nbsp;Bugzilla.&nbsp;Curiously,&nbsp;the&nbsp;"program"<br>
 (product)&nbsp;field&nbsp;is&nbsp;the&nbsp;full&nbsp;name&nbsp;of&nbsp;the&nbsp;product,&nbsp;rather&nbsp;than&nbsp;some&nbsp;other&nbsp;unique<br>
 identifier,&nbsp;like&nbsp;bug_id&nbsp;and&nbsp;user_id&nbsp;are&nbsp;elsewhere&nbsp;in&nbsp;the&nbsp;database.<br>
 <br>
 dependencies:&nbsp;Stores&nbsp;data&nbsp;about&nbsp;those&nbsp;cool&nbsp;dependency&nbsp;trees.<br>
 <br>
 fielddefs:&nbsp;&nbsp;A&nbsp;nifty&nbsp;table&nbsp;that&nbsp;defines&nbsp;other&nbsp;tables.&nbsp;For&nbsp;instance,&nbsp;when&nbsp;you<br>
 submit&nbsp;a&nbsp;form&nbsp;that&nbsp;changes&nbsp;the&nbsp;value&nbsp;of&nbsp;"AssignedTo"&nbsp;this&nbsp;table&nbsp;allows<br>
 translation&nbsp;to&nbsp;the&nbsp;actual&nbsp;field&nbsp;name&nbsp;"assigned_to"&nbsp;for&nbsp;entry&nbsp;into&nbsp;MySQL.<br>
 <br>
 groups:&nbsp;&nbsp;defines&nbsp;bitmasks&nbsp;for&nbsp;groups.&nbsp;A&nbsp;bitmask&nbsp;is&nbsp;a&nbsp;number&nbsp;that&nbsp;can&nbsp;uniquely<br>
 identify&nbsp;group&nbsp;memberships.&nbsp;For&nbsp;instance,&nbsp;say&nbsp;the&nbsp;group&nbsp;that&nbsp;is&nbsp;allowed&nbsp;to<br>
 tweak&nbsp;parameters&nbsp;is&nbsp;assigned&nbsp;a&nbsp;value&nbsp;of&nbsp;"1",&nbsp;the&nbsp;group&nbsp;that&nbsp;is&nbsp;allowed&nbsp;to&nbsp;edit<br>
 users&nbsp;is&nbsp;assigned&nbsp;a&nbsp;"2",&nbsp;and&nbsp;the&nbsp;group&nbsp;that&nbsp;is&nbsp;allowed&nbsp;to&nbsp;create&nbsp;new&nbsp;groups&nbsp;is<br>
 assigned&nbsp;the&nbsp;bitmask&nbsp;of&nbsp;"4".&nbsp;By&nbsp;uniquely&nbsp;combining&nbsp;the&nbsp;group&nbsp;bitmasks&nbsp;(much<br>
 like&nbsp;the&nbsp;chmod&nbsp;command&nbsp;in&nbsp;UNIX,)&nbsp;you&nbsp;can&nbsp;identify&nbsp;a&nbsp;user&nbsp;is&nbsp;allowed&nbsp;to&nbsp;tweak<br>
 parameters&nbsp;and&nbsp;create&nbsp;groups,&nbsp;but&nbsp;not&nbsp;edit&nbsp;users,&nbsp;by&nbsp;giving&nbsp;him&nbsp;a&nbsp;bitmask&nbsp;of<br>
 "5",&nbsp;or&nbsp;a&nbsp;user&nbsp;allowed&nbsp;to&nbsp;edit&nbsp;users&nbsp;and&nbsp;create&nbsp;groups,&nbsp;but&nbsp;not&nbsp;tweak<br>
 parameters,&nbsp;by&nbsp;giving&nbsp;him&nbsp;a&nbsp;bitmask&nbsp;of&nbsp;"6"&nbsp;Simple,&nbsp;huh?<br>
 &nbsp;&nbsp;If&nbsp;this&nbsp;makes&nbsp;no&nbsp;sense&nbsp;to&nbsp;you,&nbsp;try&nbsp;this&nbsp;at&nbsp;the&nbsp;mysql&nbsp;prompt:<br>
 mysql&#62;&nbsp;select&nbsp;*&nbsp;from&nbsp;groups;<br>
 &nbsp;&nbsp;You'll&nbsp;see&nbsp;the&nbsp;list,&nbsp;it&nbsp;makes&nbsp;much&nbsp;more&nbsp;sense&nbsp;that&nbsp;way.<br>
 <br>
 keyworddefs:&nbsp;&nbsp;Definitions&nbsp;of&nbsp;keywords&nbsp;to&nbsp;be&nbsp;used<br>
 <br>
 keywords:&nbsp;Unlike&nbsp;what&nbsp;you'd&nbsp;think,&nbsp;this&nbsp;table&nbsp;holds&nbsp;which&nbsp;keywords&nbsp;are<br>
 associated&nbsp;with&nbsp;which&nbsp;bug&nbsp;id's.<br>
 <br>
 logincookies:&nbsp;This&nbsp;stores&nbsp;every&nbsp;login&nbsp;cookie&nbsp;ever&nbsp;assigned&nbsp;to&nbsp;you&nbsp;for&nbsp;every<br>
 machine&nbsp;you've&nbsp;ever&nbsp;logged&nbsp;into&nbsp;Bugzilla&nbsp;from.&nbsp;Curiously,&nbsp;it&nbsp;never&nbsp;does&nbsp;any<br>
 housecleaning&nbsp;--&nbsp;I&nbsp;see&nbsp;cookies&nbsp;in&nbsp;this&nbsp;file&nbsp;I've&nbsp;not&nbsp;used&nbsp;for&nbsp;months.&nbsp;However,<br>
 since&nbsp;Bugzilla&nbsp;never&nbsp;expires&nbsp;your&nbsp;cookie&nbsp;(for&nbsp;convenience'&nbsp;sake),&nbsp;it&nbsp;makes<br>
 sense.<br>
 <br>
 longdescs:&nbsp;&nbsp;The&nbsp;meat&nbsp;of&nbsp;bugzilla&nbsp;--&nbsp;here&nbsp;is&nbsp;where&nbsp;all&nbsp;user&nbsp;comments&nbsp;are&nbsp;stored!<br>
 You've&nbsp;only&nbsp;got&nbsp;2^24&nbsp;bytes&nbsp;per&nbsp;comment&nbsp;(it's&nbsp;a&nbsp;mediumtext&nbsp;field),&nbsp;so&nbsp;speak<br>
 sparingly&nbsp;--&nbsp;that's&nbsp;only&nbsp;the&nbsp;amount&nbsp;of&nbsp;space&nbsp;the&nbsp;Old&nbsp;Testament&nbsp;from&nbsp;the&nbsp;Bible<br>
 would&nbsp;take&nbsp;(uncompressed,&nbsp;16&nbsp;megabytes).&nbsp;Each&nbsp;comment&nbsp;is&nbsp;keyed&nbsp;to&nbsp;the<br>
 bug_id&nbsp;to&nbsp;which&nbsp;it's&nbsp;attached,&nbsp;so&nbsp;the&nbsp;order&nbsp;is&nbsp;necessarily&nbsp;chronological,&nbsp;for<br>
 comments&nbsp;are&nbsp;played&nbsp;back&nbsp;in&nbsp;the&nbsp;order&nbsp;in&nbsp;which&nbsp;they&nbsp;are&nbsp;received.<br>
 <br>
 milestones:&nbsp;&nbsp;Interesting&nbsp;that&nbsp;milestones&nbsp;are&nbsp;associated&nbsp;with&nbsp;a&nbsp;specific&nbsp;product<br>
 in&nbsp;this&nbsp;table,&nbsp;but&nbsp;Bugzilla&nbsp;does&nbsp;not&nbsp;yet&nbsp;support&nbsp;differing&nbsp;milestones&nbsp;by<br>
 product&nbsp;through&nbsp;the&nbsp;standard&nbsp;configuration&nbsp;interfaces.<br>
 <br>
 namedqueries:&nbsp;&nbsp;This&nbsp;is&nbsp;where&nbsp;everybody&nbsp;stores&nbsp;their&nbsp;"custom&nbsp;queries".&nbsp;Very<br>
 cool&nbsp;feature;&nbsp;it&nbsp;beats&nbsp;the&nbsp;tar&nbsp;out&nbsp;of&nbsp;having&nbsp;to&nbsp;bookmark&nbsp;each&nbsp;cool&nbsp;query&nbsp;you<br>
 construct.<br>
 <br>
 products:&nbsp;&nbsp;What&nbsp;products&nbsp;you&nbsp;have,&nbsp;whether&nbsp;new&nbsp;bug&nbsp;entries&nbsp;are&nbsp;allowed&nbsp;for&nbsp;the<br>
 product,&nbsp;what&nbsp;milestone&nbsp;you're&nbsp;working&nbsp;toward&nbsp;on&nbsp;that&nbsp;product,&nbsp;votes,&nbsp;etc.&nbsp;It<br>
 will&nbsp;be&nbsp;nice&nbsp;when&nbsp;the&nbsp;components&nbsp;table&nbsp;supports&nbsp;these&nbsp;same&nbsp;features,&nbsp;so&nbsp;you<br>
 could&nbsp;close&nbsp;a&nbsp;particular&nbsp;component&nbsp;for&nbsp;bug&nbsp;entry&nbsp;without&nbsp;having&nbsp;to&nbsp;close&nbsp;an<br>
 entire&nbsp;product...<br>
 <br>
 profiles:&nbsp;&nbsp;Ahh,&nbsp;so&nbsp;you&nbsp;were&nbsp;wondering&nbsp;where&nbsp;your&nbsp;precious&nbsp;user&nbsp;information&nbsp;was<br>
 stored?&nbsp;&nbsp;Here&nbsp;it&nbsp;is!&nbsp;&nbsp;With&nbsp;the&nbsp;passwords&nbsp;in&nbsp;plain&nbsp;text&nbsp;for&nbsp;all&nbsp;to&nbsp;see!&nbsp;(but<br>
 sshh...&nbsp;don't&nbsp;tell&nbsp;your&nbsp;users!)<br>
 <br>
 profiles_activity:&nbsp;&nbsp;Need&nbsp;to&nbsp;know&nbsp;who&nbsp;did&nbsp;what&nbsp;when&nbsp;to&nbsp;who's&nbsp;profile?&nbsp;&nbsp;This'll<br>
 tell&nbsp;you,&nbsp;it's&nbsp;a&nbsp;pretty&nbsp;complete&nbsp;history.<br>
 <br>
 versions:&nbsp;&nbsp;Version&nbsp;information&nbsp;for&nbsp;every&nbsp;product<br>
 <br>
 votes:&nbsp;&nbsp;Who&nbsp;voted&nbsp;for&nbsp;what&nbsp;when<br>
 <br>
 watch:&nbsp;&nbsp;Who&nbsp;(according&nbsp;to&nbsp;userid)&nbsp;is&nbsp;watching&nbsp;who's&nbsp;bugs&nbsp;(according&nbsp;to&nbsp;their<br>
 userid).<br>
 <br>
 <br>
 ===<br>
 THE&nbsp;DETAILS<br>
 ===<br>
 <br>
 &nbsp;&nbsp;Ahh,&nbsp;so&nbsp;you're&nbsp;wondering&nbsp;just&nbsp;what&nbsp;to&nbsp;do&nbsp;with&nbsp;the&nbsp;information&nbsp;above?&nbsp;&nbsp;At&nbsp;the<br>
 mysql&nbsp;prompt,&nbsp;you&nbsp;can&nbsp;view&nbsp;any&nbsp;information&nbsp;about&nbsp;the&nbsp;columns&nbsp;in&nbsp;a&nbsp;table&nbsp;with<br>
 this&nbsp;command&nbsp;(where&nbsp;"table"&nbsp;is&nbsp;the&nbsp;name&nbsp;of&nbsp;the&nbsp;table&nbsp;you&nbsp;wish&nbsp;to&nbsp;view):<br>
 <br>
 mysql&#62;&nbsp;show&nbsp;columns&nbsp;from&nbsp;table;<br>
 <br>
 &nbsp;&nbsp;You&nbsp;can&nbsp;also&nbsp;view&nbsp;all&nbsp;the&nbsp;data&nbsp;in&nbsp;a&nbsp;table&nbsp;with&nbsp;this&nbsp;command:<br>
 <br>
 mysql&#62;&nbsp;select&nbsp;*&nbsp;from&nbsp;table;<br>
 <br>
 &nbsp;&nbsp;--&nbsp;note:&nbsp;this&nbsp;is&nbsp;a&nbsp;very&nbsp;bad&nbsp;idea&nbsp;to&nbsp;do&nbsp;on,&nbsp;for&nbsp;instance,&nbsp;the&nbsp;"bugs"&nbsp;table&nbsp;if<br>
 you&nbsp;have&nbsp;50,000&nbsp;bugs.&nbsp;You'll&nbsp;be&nbsp;sitting&nbsp;there&nbsp;a&nbsp;while&nbsp;until&nbsp;you&nbsp;ctrl-c&nbsp;or<br>
 50,000&nbsp;bugs&nbsp;play&nbsp;across&nbsp;your&nbsp;screen.<br>
 <br>
 &nbsp;&nbsp;You&nbsp;can&nbsp;limit&nbsp;the&nbsp;display&nbsp;from&nbsp;above&nbsp;a&nbsp;little&nbsp;with&nbsp;the&nbsp;command,&nbsp;where<br>
 "column"&nbsp;is&nbsp;the&nbsp;name&nbsp;of&nbsp;the&nbsp;column&nbsp;for&nbsp;which&nbsp;you&nbsp;wish&nbsp;to&nbsp;restrict&nbsp;information:<br>
 <br>
 mysql&#62;&nbsp;select&nbsp;*&nbsp;from&nbsp;table&nbsp;where&nbsp;(column&nbsp;=&nbsp;"some&nbsp;info");<br>
 <br>
 &nbsp;&nbsp;--&nbsp;or&nbsp;the&nbsp;reverse&nbsp;of&nbsp;this<br>
 <br>
 mysql&#62;&nbsp;select&nbsp;*&nbsp;from&nbsp;table&nbsp;where&nbsp;(column&nbsp;!=&nbsp;"some&nbsp;info");<br>
 <br>
 &nbsp;&nbsp;Let's&nbsp;take&nbsp;our&nbsp;example&nbsp;from&nbsp;the&nbsp;introduction,&nbsp;and&nbsp;assume&nbsp;you&nbsp;need&nbsp;to&nbsp;change<br>
 the&nbsp;word&nbsp;"verified"&nbsp;to&nbsp;"approved"&nbsp;in&nbsp;the&nbsp;resolution&nbsp;field.&nbsp;We&nbsp;know&nbsp;from&nbsp;the<br>
 above&nbsp;information&nbsp;that&nbsp;the&nbsp;resolution&nbsp;is&nbsp;likely&nbsp;to&nbsp;be&nbsp;stored&nbsp;in&nbsp;the&nbsp;"bugs"<br>
 table.&nbsp;Note&nbsp;we'll&nbsp;need&nbsp;to&nbsp;change&nbsp;a&nbsp;little&nbsp;perl&nbsp;code&nbsp;as&nbsp;well&nbsp;as&nbsp;this&nbsp;database<br>
 change,&nbsp;but&nbsp;I&nbsp;won't&nbsp;plunge&nbsp;into&nbsp;that&nbsp;in&nbsp;this&nbsp;document.&nbsp;Let's&nbsp;verify&nbsp;the<br>
 information&nbsp;is&nbsp;stored&nbsp;in&nbsp;the&nbsp;"bugs"&nbsp;table:<br>
 <br>
 mysql&#62;&nbsp;show&nbsp;columns&nbsp;from&nbsp;bugs<br>
 <br>
 &nbsp;&nbsp;(exceedingly&nbsp;long&nbsp;output&nbsp;truncated&nbsp;here)<br>
 |&nbsp;bug_status|&nbsp;enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL&nbsp;|&nbsp;UNCONFIRMED||<br>
 <br>
 &nbsp;&nbsp;Sorry&nbsp;about&nbsp;that&nbsp;long&nbsp;line.&nbsp;We&nbsp;see&nbsp;from&nbsp;this&nbsp;that&nbsp;the&nbsp;"bug&nbsp;status"&nbsp;column&nbsp;is<br>
 an&nbsp;"enum&nbsp;field",&nbsp;which&nbsp;is&nbsp;a&nbsp;MySQL&nbsp;peculiarity&nbsp;where&nbsp;a&nbsp;string&nbsp;type&nbsp;field&nbsp;can<br>
 only&nbsp;have&nbsp;certain&nbsp;types&nbsp;of&nbsp;entries.&nbsp;While&nbsp;I&nbsp;think&nbsp;this&nbsp;is&nbsp;very&nbsp;cool,&nbsp;it's&nbsp;not<br>
 standard&nbsp;SQL.&nbsp;Anyway,&nbsp;we&nbsp;need&nbsp;to&nbsp;add&nbsp;the&nbsp;possible&nbsp;enum&nbsp;field&nbsp;entry<br>
 'APPROVED'&nbsp;by&nbsp;altering&nbsp;the&nbsp;"bugs"&nbsp;table.<br>
 <br>
 mysql&#62;&nbsp;ALTER&nbsp;table&nbsp;bugs&nbsp;CHANGE&nbsp;bug_status&nbsp;bug_status<br>
 &nbsp;&nbsp;&nbsp;&nbsp;-&#62;&nbsp;enum("UNCONFIRMED",&nbsp;"NEW",&nbsp;"ASSIGNED",&nbsp;"REOPENED",&nbsp;"RESOLVED",<br>
 &nbsp;&nbsp;&nbsp;&nbsp;-&#62;&nbsp;"VERIFIED",&nbsp;"APPROVED",&nbsp;"CLOSED")&nbsp;not&nbsp;null;<br>
 <br>
 &nbsp;&nbsp;&nbsp;&nbsp;(note&nbsp;we&nbsp;can&nbsp;take&nbsp;three&nbsp;lines&nbsp;or&nbsp;more&nbsp;--&nbsp;whatever&nbsp;you&nbsp;put&nbsp;in&nbsp;before&nbsp;the<br>
 semicolon&nbsp;is&nbsp;evaluated&nbsp;as&nbsp;a&nbsp;single&nbsp;expression)<br>
 <br>
 Now&nbsp;if&nbsp;you&nbsp;do&nbsp;this:<br>
 <br>
 mysql&#62;&nbsp;show&nbsp;columns&nbsp;from&nbsp;bugs;<br>
 <br>
 &nbsp;&nbsp;you'll&nbsp;see&nbsp;that&nbsp;the&nbsp;bug_status&nbsp;field&nbsp;has&nbsp;an&nbsp;extra&nbsp;"APPROVED"&nbsp;enum&nbsp;that's<br>
 available!&nbsp;&nbsp;Cool&nbsp;thing,&nbsp;too,&nbsp;is&nbsp;that&nbsp;this&nbsp;is&nbsp;reflected&nbsp;on&nbsp;your&nbsp;query&nbsp;page&nbsp;as<br>
 well&nbsp;--&nbsp;you&nbsp;can&nbsp;query&nbsp;by&nbsp;the&nbsp;new&nbsp;status.&nbsp;But&nbsp;how's&nbsp;it&nbsp;fit&nbsp;into&nbsp;the&nbsp;existing<br>
 scheme&nbsp;of&nbsp;things?<br>
 &nbsp;&nbsp;Looks&nbsp;like&nbsp;you&nbsp;need&nbsp;to&nbsp;go&nbsp;back&nbsp;and&nbsp;look&nbsp;for&nbsp;instances&nbsp;of&nbsp;the&nbsp;word&nbsp;"verified"<br>
 in&nbsp;the&nbsp;perl&nbsp;code&nbsp;for&nbsp;Bugzilla&nbsp;--&nbsp;wherever&nbsp;you&nbsp;find&nbsp;"verified",&nbsp;change&nbsp;it&nbsp;to<br>
 "approved"&nbsp;and&nbsp;you're&nbsp;in&nbsp;business&nbsp;(make&nbsp;sure&nbsp;that's&nbsp;a&nbsp;case-insensitive&nbsp;search).<br>
 Although&nbsp;you&nbsp;can&nbsp;query&nbsp;by&nbsp;the&nbsp;enum&nbsp;field,&nbsp;you&nbsp;can't&nbsp;give&nbsp;something&nbsp;a&nbsp;status<br>
 of&nbsp;"APPROVED"&nbsp;until&nbsp;you&nbsp;make&nbsp;the&nbsp;perl&nbsp;changes.&nbsp;Note&nbsp;that&nbsp;this&nbsp;change&nbsp;I<br>
 mentioned&nbsp;can&nbsp;also&nbsp;be&nbsp;done&nbsp;by&nbsp;editing&nbsp;checksetup.pl,&nbsp;which&nbsp;automates&nbsp;a&nbsp;lot&nbsp;of<br>
 this.&nbsp;But&nbsp;you&nbsp;need&nbsp;to&nbsp;know&nbsp;this&nbsp;stuff&nbsp;anyway,&nbsp;right?<br>
 	</P
 ></DIV
 ></DIV
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"
 ><HR
 ALIGN="LEFT"
 WIDTH="100%"><TABLE
 SUMMARY="Footer navigation table"
 WIDTH="100%"
 BORDER="0"
 CELLPADDING="0"
 CELLSPACING="0"
 ><TR
 ><TD
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
 HREF="dbmodify.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
 VALIGN="top"
 ><A
 HREF="index.html"
 ACCESSKEY="H"
 >Home</A
 ></TD
 ><TD
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
 HREF="integration.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
 ></TR
 ><TR
 ><TD
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 >Modifying Your Running System</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
 VALIGN="top"
 ><A
 HREF="customization.html"
 ACCESSKEY="U"
 >Up</A
 ></TD
 ><TD
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 >Integrating Bugzilla with Third-Party Tools</TD
 ></TR
 ></TABLE
 ></DIV
 ></BODY
 ></HTML
 >
	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
	<HTML
	><HEAD
	><TITLE
	>MySQL Bugzilla Database Introduction</TITLE
	><META
	NAME="GENERATOR"
	CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
	REL="HOME"
	TITLE="The Bugzilla Guide - 2.20.1
	Release"
	HREF="index.html"><LINK
	REL="UP"
	TITLE="Customising Bugzilla"
	HREF="customization.html"><LINK
	REL="PREVIOUS"
	TITLE="Modifying Your Running System"
	HREF="dbmodify.html"><LINK
	REL="NEXT"
	TITLE="Integrating Bugzilla with Third-Party Tools"
	HREF="integration.html"></HEAD
	><BODY
	CLASS="section"
	BGCOLOR="#FFFFFF"
	TEXT="#000000"
	LINK="#0000FF"
	VLINK="#840084"
	ALINK="#0000FF"
	><DIV
	CLASS="NAVHEADER"
	><TABLE
	SUMMARY="Header navigation table"
	WIDTH="100%"
	BORDER="0"
	CELLPADDING="0"
	CELLSPACING="0"
	><TR
	><TH
	COLSPAN="3"
	ALIGN="center"
	>The Bugzilla Guide - 2.20.1
	Release</TH
	></TR
	><TR
	><TD
	WIDTH="10%"
	ALIGN="left"
	VALIGN="bottom"
	><A
	HREF="dbmodify.html"
	ACCESSKEY="P"
	>Prev</A
	></TD
	><TD
	WIDTH="80%"
	ALIGN="center"
	VALIGN="bottom"
	>Chapter 5. Customising Bugzilla</TD
	><TD
	WIDTH="10%"
	ALIGN="right"
	VALIGN="bottom"
	><A
	HREF="integration.html"
	ACCESSKEY="N"
	>Next</A
	></TD
	></TR
	></TABLE
	><HR
	ALIGN="LEFT"
	WIDTH="100%"></DIV
	><DIV
	CLASS="section"
	><H1
	CLASS="section"
	><A
	NAME="dbdoc"
	>5.5. MySQL Bugzilla Database Introduction</A
	></H1
	><P
	>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.</P
	><P
	>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.</P
	><P
	>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.</P
	><P
	>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!</P
	><P
	>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'."</P
	><P
	>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."</P
	><P
	>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...</P
	><P
	>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!</P
	><DIV
	CLASS="section"
	><H2
	CLASS="section"
	><A
	NAME="AEN2062"
	>5.5.1. Bugzilla Database Basics</A
	></H2
	><P
	>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
	<SPAN
	CLASS="QUOTE"
	>"bigint"</SPAN
	>

	and a
	<SPAN
	CLASS="QUOTE"
	>"tinyint"</SPAN
	>

	entry in MySQL. I recommend you refer to the
	<A
	HREF="http://www.mysql.com/documentation/"
	TARGET="_top"
	>MySQL documentation</A
	>
	. Below are the basics you need to know about the Bugzilla database.
	Check the chart above for more details.</P
	><P
	> <P
	></P
	><OL
	TYPE="1"
	><LI
	><P
	>To connect to your database:</P
	><P
	> <SAMP
	CLASS="prompt"
	>bash#</SAMP
	>

	<B
	CLASS="command"
	>mysql</B
	>

	<VAR
	CLASS="parameter"
	>-u root</VAR
	>
	</P
	><P
	>If this works without asking you for a password,
	<EM
	>shame on you</EM
	>

	! 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
	<A
	HREF="http://www.mysql.com/php/manual.php3?section=Privilege_system"
	TARGET="_top"
	>MySQL
	searchable documentation</A
	>.
	</P
	></LI
	><LI
	><P
	>You should now be at a prompt that looks like this:</P
	><P
	> <SAMP
	CLASS="prompt"
	>mysql></SAMP
	>
	</P
	><P
	>At the prompt, if
	<SPAN
	CLASS="QUOTE"
	>"bugs"</SPAN
	>

	is the name you chose in the
	<TT
	CLASS="filename"
	>localconfig</TT
	>

	file for your Bugzilla database, type:</P
	><P
	> <SAMP
	CLASS="prompt"
	>mysql</SAMP
	>

	<B
	CLASS="command"
	>use bugs;</B
	>
	</P
	></LI
	></OL
	>
	</P
	><DIV
	CLASS="section"
	><H3
	CLASS="section"
	><A
	NAME="AEN2089"
	>5.5.1.1. Bugzilla Database Tables</A
	></H3
	><P
	>Imagine your MySQL database as a series of spreadsheets, and
	you won't be too far off. If you use this command:</P
	><P
	> <SAMP
	CLASS="prompt"
	>mysql></SAMP
	>
	<B
	CLASS="command"
	>show tables from bugs;</B
	>
	</P
	><P
	>you'll be able to see the names of all the
	<SPAN
	CLASS="QUOTE"
	>"spreadsheets"</SPAN
	>
	(tables) in your database.</P
	><P
	>From the command issued above, ou should have some
	output that looks like this:
	<TABLE
	BORDER="0"
	BGCOLOR="#E0E0E0"
	WIDTH="100%"
	><TR
	><TD
	><FONT
	COLOR="#000000"
	><PRE
	CLASS="programlisting"
	> +-------------------+
	\| Tables in bugs \|
	+-------------------+
	\| attachments \|
	\| bugs \|
	\| bugs_activity \|
	\| cc \|
	\| components \|
	\| dependencies \|
	\| fielddefs \|
	\| groups \|
	\| keyworddefs \|
	\| keywords \|
	\| logincookies \|
	\| longdescs \|
	\| milestones \|
	\| namedqueries \|
	\| products \|
	\| profiles \|
	\| profiles_activity \|
	\| tokens \|
	\| versions \|
	\| votes \|
	\| watch \|
	+-------------------+
	</PRE
	></FONT
	></TD
	></TR
	></TABLE
	>
	</P
	><P
	CLASS="literallayout"
	><br>
	Here's an overview of what each table does. Most columns in each table have<br>
	descriptive names that make it fairly trivial to figure out their jobs.<br>
	<br>
	attachments: This table stores all attachments to bugs. It tends to be your<br>
	largest table, yet also generally has the fewest entries because file<br>
	attachments are so (relatively) large.<br>
	<br>
	bugs:  This is the core of your system. The bugs table stores most of the<br>
	current information about a bug, with the exception of the info stored in the<br>
	other tables.<br>
	<br>
	bugs_activity:  This stores information regarding what changes are made to bugs<br>
	when -- a history file.<br>
	<br>
	cc:  This tiny table simply stores all the CC information for any bug which has<br>
	any entries in the CC field of the bug. Note that, like most other tables in<br>
	Bugzilla, it does not refer to users by their user names, but by their unique<br>
	userid, stored as a primary key in the profiles table.<br>
	<br>
	components: This stores the programs and components (or products and<br>
	components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program"<br>
	(product) field is the full name of the product, rather than some other unique<br>
	identifier, like bug_id and user_id are elsewhere in the database.<br>
	<br>
	dependencies: Stores data about those cool dependency trees.<br>
	<br>
	fielddefs:  A nifty table that defines other tables. For instance, when you<br>
	submit a form that changes the value of "AssignedTo" this table allows<br>
	translation to the actual field name "assigned_to" for entry into MySQL.<br>
	<br>
	groups:  defines bitmasks for groups. A bitmask is a number that can uniquely<br>
	identify group memberships. For instance, say the group that is allowed to<br>
	tweak parameters is assigned a value of "1", the group that is allowed to edit<br>
	users is assigned a "2", and the group that is allowed to create new groups is<br>
	assigned the bitmask of "4". By uniquely combining the group bitmasks (much<br>
	like the chmod command in UNIX,) you can identify a user is allowed to tweak<br>
	parameters and create groups, but not edit users, by giving him a bitmask of<br>
	"5", or a user allowed to edit users and create groups, but not tweak<br>
	parameters, by giving him a bitmask of "6" Simple, huh?<br>
	If this makes no sense to you, try this at the mysql prompt:<br>
	mysql> select * from groups;<br>
	You'll see the list, it makes much more sense that way.<br>
	<br>
	keyworddefs:  Definitions of keywords to be used<br>
	<br>
	keywords: Unlike what you'd think, this table holds which keywords are<br>
	associated with which bug id's.<br>
	<br>
	logincookies: This stores every login cookie ever assigned to you for every<br>
	machine you've ever logged into Bugzilla from. Curiously, it never does any<br>
	housecleaning -- I see cookies in this file I've not used for months. However,<br>
	since Bugzilla never expires your cookie (for convenience' sake), it makes<br>
	sense.<br>
	<br>
	longdescs:  The meat of bugzilla -- here is where all user comments are stored!<br>
	You've only got 2^24 bytes per comment (it's a mediumtext field), so speak<br>
	sparingly -- that's only the amount of space the Old Testament from the Bible<br>
	would take (uncompressed, 16 megabytes). Each comment is keyed to the<br>
	bug_id to which it's attached, so the order is necessarily chronological, for<br>
	comments are played back in the order in which they are received.<br>
	<br>
	milestones:  Interesting that milestones are associated with a specific product<br>
	in this table, but Bugzilla does not yet support differing milestones by<br>
	product through the standard configuration interfaces.<br>
	<br>
	namedqueries:  This is where everybody stores their "custom queries". Very<br>
	cool feature; it beats the tar out of having to bookmark each cool query you<br>
	construct.<br>
	<br>
	products:  What products you have, whether new bug entries are allowed for the<br>
	product, what milestone you're working toward on that product, votes, etc. It<br>
	will be nice when the components table supports these same features, so you<br>
	could close a particular component for bug entry without having to close an<br>
	entire product...<br>
	<br>
	profiles:  Ahh, so you were wondering where your precious user information was<br>
	stored?  Here it is!  With the passwords in plain text for all to see! (but<br>
	sshh... don't tell your users!)<br>
	<br>
	profiles_activity:  Need to know who did what when to who's profile?  This'll<br>
	tell you, it's a pretty complete history.<br>
	<br>
	versions:  Version information for every product<br>
	<br>
	votes:  Who voted for what when<br>
	<br>
	watch:  Who (according to userid) is watching who's bugs (according to their<br>
	userid).<br>
	<br>
	<br>
	===<br>
	THE DETAILS<br>
	===<br>
	<br>
	Ahh, so you're wondering just what to do with the information above?  At the<br>
	mysql prompt, you can view any information about the columns in a table with<br>
	this command (where "table" is the name of the table you wish to view):<br>
	<br>
	mysql> show columns from table;<br>
	<br>
	You can also view all the data in a table with this command:<br>
	<br>
	mysql> select * from table;<br>
	<br>
	-- note: this is a very bad idea to do on, for instance, the "bugs" table if<br>
	you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or<br>
	50,000 bugs play across your screen.<br>
	<br>
	You can limit the display from above a little with the command, where<br>
	"column" is the name of the column for which you wish to restrict information:<br>
	<br>
	mysql> select * from table where (column = "some info");<br>
	<br>
	-- or the reverse of this<br>
	<br>
	mysql> select * from table where (column != "some info");<br>
	<br>
	Let's take our example from the introduction, and assume you need to change<br>
	the word "verified" to "approved" in the resolution field. We know from the<br>
	above information that the resolution is likely to be stored in the "bugs"<br>
	table. Note we'll need to change a little perl code as well as this database<br>
	change, but I won't plunge into that in this document. Let's verify the<br>
	information is stored in the "bugs" table:<br>
	<br>
	mysql> show columns from bugs<br>
	<br>
	(exceedingly long output truncated here)<br>
	\| bug_status\| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')\|\|MUL \| UNCONFIRMED\|\|<br>
	<br>
	Sorry about that long line. We see from this that the "bug status" column is<br>
	an "enum field", which is a MySQL peculiarity where a string type field can<br>
	only have certain types of entries. While I think this is very cool, it's not<br>
	standard SQL. Anyway, we need to add the possible enum field entry<br>
	'APPROVED' by altering the "bugs" table.<br>
	<br>
	mysql> ALTER table bugs CHANGE bug_status bug_status<br>
	-> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",<br>
	-> "VERIFIED", "APPROVED", "CLOSED") not null;<br>
	<br>
	(note we can take three lines or more -- whatever you put in before the<br>
	semicolon is evaluated as a single expression)<br>
	<br>
	Now if you do this:<br>
	<br>
	mysql> show columns from bugs;<br>
	<br>
	you'll see that the bug_status field has an extra "APPROVED" enum that's<br>
	available!  Cool thing, too, is that this is reflected on your query page as<br>
	well -- you can query by the new status. But how's it fit into the existing<br>
	scheme of things?<br>
	Looks like you need to go back and look for instances of the word "verified"<br>
	in the perl code for Bugzilla -- wherever you find "verified", change it to<br>
	"approved" and you're in business (make sure that's a case-insensitive search).<br>
	Although you can query by the enum field, you can't give something a status<br>
	of "APPROVED" until you make the perl changes. Note that this change I<br>
	mentioned can also be done by editing checksetup.pl, which automates a lot of<br>
	this. But you need to know this stuff anyway, right?<br>
	</P
	></DIV
	></DIV
	></DIV
	><DIV
	CLASS="NAVFOOTER"
	><HR
	ALIGN="LEFT"
	WIDTH="100%"><TABLE
	SUMMARY="Footer navigation table"
	WIDTH="100%"
	BORDER="0"
	CELLPADDING="0"
	CELLSPACING="0"
	><TR
	><TD
	WIDTH="33%"
	ALIGN="left"
	VALIGN="top"
	><A
	HREF="dbmodify.html"
	ACCESSKEY="P"
	>Prev</A
	></TD
	><TD
	WIDTH="34%"
	ALIGN="center"
	VALIGN="top"
	><A
	HREF="index.html"
	ACCESSKEY="H"
	>Home</A
	></TD
	><TD
	WIDTH="33%"
	ALIGN="right"
	VALIGN="top"
	><A
	HREF="integration.html"
	ACCESSKEY="N"
	>Next</A
	></TD
	></TR
	><TR
	><TD
	WIDTH="33%"
	ALIGN="left"
	VALIGN="top"
	>Modifying Your Running System</TD
	><TD
	WIDTH="34%"
	ALIGN="center"
	VALIGN="top"
	><A
	HREF="customization.html"
	ACCESSKEY="U"
	>Up</A
	></TD
	><TD
	WIDTH="33%"
	ALIGN="right"
	VALIGN="top"
	>Integrating Bugzilla with Third-Party Tools</TD
	></TR
	></TABLE
	></DIV
	></BODY
	></HTML
	>