> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/server/reference/sql-statements/table-statements/repair-view.md).

# REPAIR VIEW

## Syntax

{% code overflow="wrap" %}

```bnf
REPAIR [NO_WRITE_TO_BINLOG | LOCAL] VIEW  view_name[, view_name] ... [FROM MYSQL]
```

{% endcode %}

## Description

The `REPAIR VIEW` statement checks whether the view algorithm is correct. It is run as part of [mariadb-upgrade](/docs/server/clients-and-utilities/deployment-tools/mariadb-upgrade.md), and should not normally be required in regular use.

By default it corrects the checksum and if necessary adds the mariadb-version field. If the optional `FROM MYSQL` clause is used, and no mariadb-version field is present, the `MERGE` and `TEMPTABLE` algorithms are toggled.

By default, `REPAIR VIEW` statements are written to the [binary log](/docs/server/server-management/server-monitoring-logs/binary-log.md) and will be [replicated](/docs/server/server-usage/storage-engines/myrocks/myrocks-and-replication.md). The `NO_WRITE_TO_BINLOG` keyword (`LOCAL` is an alias) will ensure the statement is not written to the binary log.

## See Also

* [CHECK VIEW](/docs/server/reference/sql-statements/table-statements/check-view.md)

<sub>*This page is licensed: CC BY-SA / Gnu FDL*</sub>

{% @marketo/form formId="4316" %}