Public Member Functions | |
| test_chado_add_mview () | |
| test_chado_delete_mview () | |
| test_chado_edit_mview () | |
| test_chado_refresh_mview () | |
| test_chado_populate_mview () | |
| test_chado_get_mview_id () | |
| test_chado_get_mview_table_names () | |
| test_chado_get_mviews () | |
| test_re_adding_deleted_mview_issue_322 () | |
| reset_tables () | |
Member Function Documentation
◆ reset_tables()
| Tests\tripal_chado\api\TripalChadoMViewsAPITest::reset_tables | ( | ) |
The chado_table_exists() function mantains a global variable to keep track of which tables exist. If the table exists then it stores that info in the global variable. This is because lots of queries perform a check to see if the tables exist and that can have a major performance hit.
Because we are creating and dropping Chado tables in our tests it throws off the array and we need to reset it. Normally this isn't a problem because this would get reset on every page load anyone. For testing it doesn't.
◆ test_chado_add_mview()
| Tests\tripal_chado\api\TripalChadoMViewsAPITest::test_chado_add_mview | ( | ) |
Test creation of a new materialized view.
@group api
◆ test_chado_delete_mview()
| Tests\tripal_chado\api\TripalChadoMViewsAPITest::test_chado_delete_mview | ( | ) |
Test deletion of a materialized view.
@group api
◆ test_chado_edit_mview()
| Tests\tripal_chado\api\TripalChadoMViewsAPITest::test_chado_edit_mview | ( | ) |
Test modifications to a materialized view
@group api
◆ test_chado_get_mview_id()
| Tests\tripal_chado\api\TripalChadoMViewsAPITest::test_chado_get_mview_id | ( | ) |
Test modifications to a materialized view
@group api
◆ test_chado_get_mview_table_names()
| Tests\tripal_chado\api\TripalChadoMViewsAPITest::test_chado_get_mview_table_names | ( | ) |
Test retrieving names of the materialized views.
@group api
◆ test_chado_get_mviews()
| Tests\tripal_chado\api\TripalChadoMViewsAPITest::test_chado_get_mviews | ( | ) |
Test retrieving all materialized view objects.
@group api
◆ test_chado_populate_mview()
| Tests\tripal_chado\api\TripalChadoMViewsAPITest::test_chado_populate_mview | ( | ) |
Test re-populating a materialized view.
@group api
◆ test_chado_refresh_mview()
| Tests\tripal_chado\api\TripalChadoMViewsAPITest::test_chado_refresh_mview | ( | ) |
Test adding a Tripal Job to re-populate a materialized view
@group api
◆ test_re_adding_deleted_mview_issue_322()
| Tests\tripal_chado\api\TripalChadoMViewsAPITest::test_re_adding_deleted_mview_issue_322 | ( | ) |
Issue 322 reported the problem of re-adding a materialized view after the actual table had been manually removed outside of Tripal. The function reported errors.
@ticket 322
The documentation for this class was generated from the following file:
- tests/tripal_chado/api/TripalChadoMViewsAPITest.php
