Forum Discussion

anandmr65's avatar
anandmr65
New Contributor
10 years ago

Reporting Views in CC

Hi,



There are many "Reporting Views" that helps us to get the data usingthe SQL..



For eg.reviewcustom.





How do I know the column names avaiable in these views and the definition of views.



Sincere request to all to help in this regard.



Thanks & REgards

Anand



The website gives info as below (http://support.smartbear.com/viewarticle/20060/)

Reporting Views


For databases that support the concept of a "View," Code Collaborator creates a set of Views specifically for the purpose of external report-writers. You should use these Views whenever possible; we will make sure that the definitions of these Views remain the same even if we change the database schema in future versions.



You can also use these Views as a guide for how to create other custom queries.



Here are the special reporting Views:







































































defects_by_path




One row per review reporting file path, lines of code reviewed, and number of defects.




defectcustom




These are the custom fields you've defined for defects, one row for each defect. If you change the custom field definition, the layout of this table will change as well (automatically, and immediately). Warning: Because the exact custom field titles are used for column names, if you change the title of a custom field it will change the definition of this view.



With review workflows, each review might have a different subset of custom fields. In this case fields are NULL when they are not applicable.




defectcustom_compat




Same as defectcustom, but column names are in the form custom_id_N where "N" is the custom field ID as displayed in the custom fields admin page. The columns are ordered exactly the same as defectcustom, so you can also tell which is which by comparing the two views.




defect_custom_dropdowns




This table contains a list of the possible values as defined in drop-down and multi-select Defect Custom Fields.




review_activity




For each unique combination of review, user, and role, reports the person-hours spent.



This includes data for current review participants only. If a user was a participant but isn't now, that person will not be included in this result. However that time will be included in the review_activity_summary view.




review_activity_summary




One row per review reporting author, reviewer, rework hours, and total person-hours spent in the review.




review_comment_summary




One row per review reporting author, reviewer, and total number of comments made in the review.




review_defect_summary




One row per review reporting the number of defects created in that review.




review_metrics_summary




One row per review reporting a variety of standard metrics such as inspection rate, defect rate, defect density, and the individual numbers used to form those ratios. Some values will contain NULL values because of divide-by-zero errors.




review_version_list




Lists all versions actually associated with a review, although with the associated review.




review_version_summary




One row per review reporting the number of files and line metrics (total, added, modified, removed) for all files in the review.




reviewcustom




These are the custom fields you've defined for reviews, one row for each review. If you change the custom field definition, the layout of this table will change as well (automatically, and immediately).



With review workflows, each review might have a different subset of custom fields. In this case fields are NULL when they are not applicable.




reviewcustom_compat




Same as reviewcustom, but column names are in the form custom_id_N where "N" is the custom field ID as displayed in the custom fields admin page. The columns are ordered exactly the same as reviewcustom, so you can also tell which is which by comparing the two views.




review_custom_dropdowns




This table contains a list of the possible values as defined in drop-down and multi-select Review Custom Fields.




userprefs




Additional user preferences, one row per user. Most user information and preferences are stored in the user table; the rest is here.




userprefs_compat




Same as userprefs, but column names are in the form custom_id_N where "N" is an internal ID used to store user preferences. The columns are ordered exactly the same as userprefs, so you can tell which is which by comparing the two views.





No RepliesBe the first to reply