Database endpoints
Drop a materialized view
Drops a materialized view and everything stored for it.
DELETE /v1/tenants/{tenant}/sql/materialized-views/{name}
- Confirm the view nameSelect the stored view to remove.
- Drop the viewRemove its definition and materialized contents.
- Read the dropped resultKeep source-table operations separate.
Before you start
Use your database bearer token.
Use the exact name of the view to remove. The example deletes demo_scores.
Path parameters
| Field | Type | Required |
|---|---|---|
tenant | string | Required |
name | string | Required |
Headers
| Field | Type | Required | Description |
|---|---|---|---|
x-oc-db-user | string | Optional | Acting database user (role, grant and row-policy checks). Send with x-oc-db-key. |
x-oc-db-key | string | Optional | API key of the x-oc-db-user user. |
Read the result
dropped confirms removal of the named view and its stored contents. This is not a request to drop the view's source table.
Response statuses
HTTP status reference
| Status | What to do |
|---|---|
| 200 | OK |
| 400 | Correct the request before retrying. |
| 401 | Check the credential and Authorization header. |
| 402 | Check feature access or available credits. |
| 403 | Check tenant access, roles and permissions. |
| 404 | Check the resource ID and API route. |
| 429 | Honor Retry-After when present; back off. |
| 500 | Check the outcome before retrying a write. |
| 501 | Check deployment support for this operation. |
| 502 | Check service availability and the write outcome. |
| 503 | Honor Retry-After when present; check write outcomes. |