Fixed bug in test, and removed old comment from API inline documentation

tests/tripal_chado/api/TripalChadoMViewsAPITest.php

@@ -206,7 +206,7 @@ class TripalChadoMViewsAPITest extends TripalTestCase {
     
     // Now try to read the mview. Previously, the behavior was the the mview
     // table would not be created because Tripal thinks it's already there.
-    chado_add_mview($mview_name, $mview_module, $mview_schema, $mview_sql, $mview_comment, FALSE);
+    $success = chado_add_mview($mview_name, $mview_module, $mview_schema, $mview_sql, $mview_comment, FALSE);
     $this->assertTrue($success, "Failed to re-create materialized view: $mview_name");
     
     $this->assertTrue(chado_table_exists($mview_name),

tripal_chado/api/tripal_chado.mviews.api.inc

@@ -16,12 +16,8 @@
  */
 
 /**
- * Add a materialized view to the chado database to help speed data access. This
- * function supports the older style where postgres column specifications
- * are provided using the $mv_table, $mv_specs and $indexed variables. It also
- * supports the newer preferred method where the materialized view is described
- * using the Drupal Schema API array.
- *
+ * Add a materialized view to the chado database. 
+ * 
  * @param $name
  *   The name of the materialized view.
  * @param $modulename
@@ -41,7 +37,8 @@
  *   parameter allows this to be used as a true API function.
  *
  * @return 
- *   TRUE if the materialized view was successfully addd, FALSE otherwise.
+ *   TRUE if the materialized view was successfully added, FALSE otherwise.
+ *   
  * @ingroup tripal_mviews_api
  */
 function chado_add_mview($name, $modulename, $mv_schema, $query, $comment = NULL, $redirect = TRUE) {