Closed Bug 314385 Opened 19 years ago Closed 19 years ago

MySQL configuration instructions result in error

Categories

(Bugzilla :: Documentation, defect)

defect
Not set
minor

Tracking

()

RESOLVED FIXED
Bugzilla 2.18

People

(Reporter: pg, Assigned: cso)

References

Details

Attachments

(2 files, 3 obsolete files)

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: Following the following Bugzilla instructions under "Configuration": By default, MySQL will limit the size of a table to 4GB. This limit is present even if the underlying filesystem has no such limit. To set a higher limit, follow these instructions. Run the MySQL command-line client and enter: mysql> ALTER TABLE attachments AVG_ROW_LENGTH=1000000, MAX_ROWS=20000; I get: ERROR 1046 (3D000): No database selected. Reproducible: Always Steps to Reproduce:
Although I would think the error message would make it obvious (tell mysql that you want to do things in the database that belongs to Bugzilla first), I suppose we could add a hint to that section of the docs... "make sure you've selected your Bugzilla database first" or something.
Component: Installation & Upgrading → Documentation
Assignee: installation → documentation
Hi, I believe documentation assumes a lot of knowledge which I ( a software engineer with 18 years of experience :) ) simply do not possess. I have never done any database administration. I assume I need to use the "use" command, but hat is the name of the bugzilla database? Your response inspired me to do a google 'sql command "show available databases"' and I found "show databases;" and I got this: mysql test but where's the bugzilla database? Thanks for your help, Pavel
Attached patch Patch v1 (obsolete) — Splinter Review
Patch v1 Clarify when to complete this step.
Assignee: documentation → colin.ogilvie
Status: UNCONFIRMED → ASSIGNED
Attachment #201367 - Flags: review?(justdave)
Attachment #201367 - Flags: review?(justdave)
Attached patch Patch v1.1 (obsolete) — Splinter Review
Actually tackle the problem... This clarifies that you should 'use $bugs_db;' first.
Attachment #201367 - Attachment is obsolete: true
Attachment #201369 - Flags: review?(justdave)
Pavel: Colin pointed out on IRC that this instruction is in the docs prior to the spot where it tell you to create the database. If the database hasn't even been created yet, then of course it's not going to work. :) And if we hadn't told you to create it yet, then you wouldn't know you'd have to. So yes, the docs are assuming you'd know something you read later in the docs when you haven't gotten to it yet, thus a problem with the docs. I hadn't realized it was all backwards when I said the above. Hope you accept my apology! :)
Comment on attachment 201369 [details] [diff] [review] Patch v1.1 How about if we combine the two patches and both point out the "after you've completed the database setup part of installation" and that you need to "use bugs".
Attachment #201369 - Flags: review?(justdave) → review-
Attached patch Patch v2 (obsolete) — Splinter Review
Combine the two patches...
Attachment #201369 - Attachment is obsolete: true
Attachment #201371 - Flags: review?(justdave)
Thanks, guys. I'm very encouraged that you take documentation seriously. Ease of installment and management is at times more important than the feature set.
Severity: normal → minor
OS: Windows XP → All
Hardware: PC → All
*** Bug 280395 has been marked as a duplicate of this bug. ***
*** Bug 331811 has been marked as a duplicate of this bug. ***
Comment on attachment 201371 [details] [diff] [review] Patch v2 This looks good, with 2 specific additions that will probably go upon checkin: -> swap those 2 questions :), especially since they are in reversed order. -> specify that the default for $bugs_db is "bugs" (the other question simply assumes default values in their example, which is also good).
Attachment #201371 - Flags: review?(justdave) → review+
Target Milestone: --- → Bugzilla 2.18
r=vladd
Attachment #201371 - Attachment is obsolete: true
Attachment #224773 - Flags: review+
Unfortunately 2.18 required a manual backport :(. Here's the patch FTR.
Attachment #224780 - Flags: review+
In the attachment v2.1 (only the version for trunk, 2.22 and 2.20) there were some tabs (coming from v2) that I've fixed upon checkin. trunk commit: Checking in docs/xml/installation.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/installation.xml,v <-- installation.xml new revision: 1.121; previous revision: 1.120 done BUGZILLA-2_22-BRANCH: Checking in docs/xml/installation.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/installation.xml,v <-- installation.xml new revision: 1.107.2.10; previous revision: 1.107.2.9 done BUGZILLA-2_20-BRANCH: Checking in docs/xml/installation.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/installation.xml,v <-- installation.xml new revision: 1.98.2.18; previous revision: 1.98.2.17 done BUGZILLA-2_18-BRANCH: Checking in docs/xml/installation.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/installation.xml,v <-- installation.xml new revision: 1.72.2.31; previous revision: 1.72.2.30 done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: