[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

09/15/2009 at 09:13AM PDT, ID: 24733439
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.2

Best Practices for MySQL Table Documentation

Asked by Ray_Paseur in PHP and Databases, MySQL Server, Enterprise Software

Tags: MySQL, Database, Documentation

This question is intended to be open ended, and references to online or published manuals are very welcome.  What are the best practices for MySQL documentation?  

In other words, if I create a table with a field named `foo` and a type of varchar(32) I have not provided very much information, but it I have some documentation that identifies `foo` as the city field of the client's mailing address, normalized against the US Postal Service names for American cities, then I have a much clearer picture of what you could expect to find in `foo`.

Where do programmers and DBAs keep this kind of information?  Is there something analogous to a DocBlock to describe columns and table relationships?  Is there some way to keep the descriptive information in the data base itself?  What are the questions I am forgetting to ask?

TIA, ~Ray
 
Keywords: Best Practices for MySQL Table Docu…
 
Loading Advertisement...
 
[+][-]09/15/09 09:22 AM, ID: 25336584

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: PHP and Databases, MySQL Server, Enterprise Software
Tags: MySQL, Database, Documentation
Sign Up Now!
Solution Provided By: nemws1
Participating Experts: 1
Solution Grade: A
 
 
[+][-]09/15/09 09:23 AM, ID: 25336590

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20091111-EE-VQP-91 - Hierarchy / EE_QW_3_20080625