How to manage materialized views in MariaDB?

MariaDB, an open-source database management system, does not inherently support materialized views – a database object that contains the results of a query. However, they can be simulated using a combination of other MariaDB features: views, temporary tables, and event schedulers.

To simulate a materialized view in MariaDB, you would:

1. Create a view of the data you want to persist.
2. Create a temporary table to contain the view’s data.
3. Create an event scheduler to refresh the temporary table at set intervals.

An example of how these components can be used to create a materialized view is provided below:

Creating View
```
CREATE VIEW example_view AS
SELECT *
FROM example_table;
```

Creating Temporary Table
```
CREATE TABLE example_materialized_view
LIKE example_view;
```

Inserting Data
```
INSERT INTO example_materialized_view
SELECT *
FROM example_view;
```

Refreshing Data
You can use an event to refresh the data by clearing out the old data and inserting the fresh data:

```
CREATE EVENT refresh_data
ON SCHEDULE EVERY 1 HOUR
DO TRUNCATE TABLE example_materialized_view; INSERT INTO example_materialized_view SELECT * FROM example_view;
```

Please note this approach has limitations, updates are periodic and not real-time, and it can take up processing time and disk space. Always make sure to define the event scheduler status to “ON” for scheduling events.

Also, note tuning is vital for optimum performance of any database. Matviews are no different; matviews in MariaDB are just regular tables that can benefit from tuning features such as partitioning, indexing, etc.

In conclusion, while MariaDB does not provide built-in support for materialized views, their functionality can be simulated relatively easily using other features provided by the database management system.