From 1b2aa767929784a37212b9e3dc01f9e119c4a9d6 Mon Sep 17 00:00:00 2001 From: "gerv%gerv.net" <> Date: Sun, 22 Dec 2002 00:33:39 +0000 Subject: Rebuild HTML and text versions of documentation for 2.17.2 release. --- docs/html/dbdoc.html | 27 ++++++++++++++------------- 1 file changed, 14 insertions(+), 13 deletions(-) (limited to 'docs/html/dbdoc.html') diff --git a/docs/html/dbdoc.html b/docs/html/dbdoc.html index 49e9b6526..f6179657d 100644 --- a/docs/html/dbdoc.html +++ b/docs/html/dbdoc.html @@ -13,8 +13,8 @@ REL="UP" TITLE="The Bugzilla Database" HREF="database.html">Prev

B.2. MySQL Bugzilla Database Introduction

B.2. MySQL Bugzilla Database Introduction

This information comes straight from my life. I was forced to learn how Bugzilla organizes database because of nitpicky requests from users @@ -133,7 +135,9 @@ CLASS="section" >

B.2.1. Bugzilla Database Basics

B.2.1. Bugzilla Database Basics

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 @@ -247,7 +251,9 @@ CLASS="section" >

B.2.1.1. Bugzilla Database Tables

B.2.1.1. Bugzilla Database Tables

Imagine your MySQL database as a series of spreadsheets, and you won't be too far off. If you use this command:

profiles_activity:  Need to know who did what when to who's profile?  This'll
tell you, it's a pretty complete history.

-shadowlog:  I could be mistaken here, but I believe this table tells you when
-your shadow database is updated and what commands were used to update it.  We
-don't use a shadow database at our site yet, so it's pretty empty for us.
-
versions:  Version information for every product

votes:  Who voted for what when
@@ -498,7 +499,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevDatabase Schema ChartModifying Your Running System