-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdata-integrity-violation.html
42 lines (41 loc) · 1.62 KB
/
data-integrity-violation.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Data Integrity Violation</title>
<link rel="shortcut icon" type="image/x-icon" href="favicon.png">
<link rel="stylesheet" href="styles.css">
<link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons">
</head>
<body onload="prettyJson()">
<script>
function prettyJson() {
var data = {
"type": "https://omni-us.github.io/API-problems/data-integrity-violation",
"title": "Data Integrity Violation",
"status": 409,
"detail": "Resource with name [example] already exists"
}
document.getElementById("json").innerHTML = JSON.stringify(data, undefined, 2);
}
</script>
<div class="w3-padding w3-xlarge back">
<a href="/API-problems"><i class="material-icons">arrow_back</i></a>
</div>
<h1 class="logo">omni:us</h1>
<div class="container">
<h1>Data Integrity Violation</h1>
<p>Syntactically and semantically correct request, but an integrity constraint has been broken.
Conflicts like these are most likely to occur in response to a <b>PUT</b> or <b>PATCH</b> request.
It is produced when a constraint which plays a role in referential integrity has been broken.</p>
<p>Example:</p>
<div class="codeblock">
<code>
<pre id="json"></pre>
</code>
</div>
</div>
</body>
</html>