summaryrefslogtreecommitdiffstats
path: root/docs/sgml/database.sgml
diff options
context:
space:
mode:
authorbarnboy%trilobyte.net <>2001-04-25 16:11:45 +0200
committerbarnboy%trilobyte.net <>2001-04-25 16:11:45 +0200
commit2d4d7c92bfb4ce18e4413b1e66f30bd62a44e6ff (patch)
treea2d82b3f59cc18d708502912933cb5689fc619fd /docs/sgml/database.sgml
parent064f6ba69bb6e46e41427cfbccb7a6839e75110e (diff)
downloadbugzilla-2d4d7c92bfb4ce18e4413b1e66f30bd62a44e6ff.tar.gz
bugzilla-2d4d7c92bfb4ce18e4413b1e66f30bd62a44e6ff.tar.xz
Updated Bugzilla Guide and README to fix bug 76156, bug 76841, and bug 26242.
The README is now gutted, pointers to Guide. Also some new sections added, old ones fixed, and notes appended to deprecated sections I've not yet had the heart to remove.
Diffstat (limited to 'docs/sgml/database.sgml')
-rw-r--r--docs/sgml/database.sgml14
1 files changed, 10 insertions, 4 deletions
diff --git a/docs/sgml/database.sgml b/docs/sgml/database.sgml
index 16c72494e..eced31c52 100644
--- a/docs/sgml/database.sgml
+++ b/docs/sgml/database.sgml
@@ -1,10 +1,10 @@
-<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<APPENDIX id="database">
<TITLE>The Bugzilla Database</TITLE>
<NOTE>
-<PARA>This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers? <REMARK>MPB</REMARK></PARA>
+<PARA>This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers?</PARA>
</NOTE>
<SECTION id="dbschema">
<TITLE>Database Schema Chart</TITLE>
@@ -405,7 +405,13 @@ http://www.devshed.com/Server_Side/MySQL/
<TITLE>MySQL Permissions & Grant Tables</TITLE>
<NOTE>
- <PARA>The following portion of documentation comes from my answer to an old discussion of Keynote, a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the Keynote support group regarding MySQL grant table permissions, and how to use them effectively. It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables since this time, but it serves as a decent introduction and troubleshooting document for grant table issues. I used Keynote to track my troubles until I discovered Bugzilla, which gave me a whole new set of troubles to work on : )</PARA>
+ <PARA>The following portion of documentation comes from my answer to an old discussion of Keystone,
+ a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the
+ Keystone support group regarding MySQL grant table permissions, and how to use them effectively.
+ It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables
+ since this time, but it serves as a decent introduction and troubleshooting document for grant
+ table issues. I used Keynote to track my troubles until I discovered Bugzilla,
+ which gave me a whole new set of troubles to work on : )</PARA>
</NOTE>
<LITERALLAYOUT>
@@ -589,7 +595,7 @@ NEW CONTACT INFORMATION:
<SECTION id="cleanupwork">
<TITLE>Cleaning up after mucking with Bugzilla</TITLE>
<LITERALLAYOUT>
-Contributed by Eric Hansen:
+Contributed by Eric Hanson:
There are several things, and one trick. There is a small tiny piece of
documentation I saw once that said something very important.
1) After pretty much any manual working of the Mysql db, you must