squawk-cli 2.8.0__py3-none-macosx_11_0_arm64.whl → 2.9.0__py3-none-macosx_11_0_arm64.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
Binary file
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: squawk-cli
|
|
3
|
-
Version: 2.
|
|
3
|
+
Version: 2.9.0
|
|
4
4
|
Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
|
|
5
5
|
Classifier: Operating System :: MacOS
|
|
6
6
|
Classifier: Operating System :: Microsoft :: Windows
|
|
@@ -63,42 +63,42 @@ warning[prefer-bigint-over-int]: Using 32-bit integer fields can result in hitti
|
|
|
63
63
|
--> example.sql:6:10
|
|
64
64
|
|
|
|
65
65
|
6 | "id" serial NOT NULL PRIMARY KEY,
|
|
66
|
-
|
|
|
66
|
+
| ------
|
|
67
67
|
|
|
|
68
68
|
= help: Use 64-bit integer values instead to prevent hitting this limit.
|
|
69
69
|
warning[prefer-identity]: Serial types make schema, dependency, and permission management difficult.
|
|
70
70
|
--> example.sql:6:10
|
|
71
71
|
|
|
|
72
72
|
6 | "id" serial NOT NULL PRIMARY KEY,
|
|
73
|
-
|
|
|
73
|
+
| ------
|
|
74
74
|
|
|
|
75
75
|
= help: Use Identity columns instead.
|
|
76
76
|
warning[prefer-text-field]: Changing the size of a `varchar` field requires an `ACCESS EXCLUSIVE` lock, that will prevent all reads and writes to the table.
|
|
77
77
|
--> example.sql:7:13
|
|
78
78
|
|
|
|
79
79
|
7 | "alpha" varchar(100) NOT NULL
|
|
80
|
-
|
|
|
80
|
+
| ------------
|
|
81
81
|
|
|
|
82
82
|
= help: Use a `TEXT` field with a `CHECK` constraint.
|
|
83
83
|
warning[require-concurrent-index-creation]: During normal index creation, table updates are blocked, but reads are still allowed.
|
|
84
84
|
--> example.sql:10:1
|
|
85
85
|
|
|
|
86
86
|
10 | CREATE INDEX "field_name_idx" ON "table_name" ("field_name");
|
|
87
|
-
|
|
|
87
|
+
| ------------------------------------------------------------
|
|
88
88
|
|
|
|
89
89
|
= help: Use `CONCURRENTLY` to avoid blocking writes.
|
|
90
90
|
warning[constraint-missing-not-valid]: By default new constraints require a table scan and block writes to the table while that scan occurs.
|
|
91
91
|
--> example.sql:12:24
|
|
92
92
|
|
|
|
93
93
|
12 | ALTER TABLE table_name ADD CONSTRAINT field_name_constraint UNIQUE (field_name);
|
|
94
|
-
|
|
|
94
|
+
| --------------------------------------------------------
|
|
95
95
|
|
|
|
96
96
|
= help: Use `NOT VALID` with a later `VALIDATE CONSTRAINT` call.
|
|
97
97
|
warning[disallowed-unique-constraint]: Adding a `UNIQUE` constraint requires an `ACCESS EXCLUSIVE` lock which blocks reads and writes to the table while the index is built.
|
|
98
98
|
--> example.sql:12:28
|
|
99
99
|
|
|
|
100
100
|
12 | ALTER TABLE table_name ADD CONSTRAINT field_name_constraint UNIQUE (field_name);
|
|
101
|
-
|
|
|
101
|
+
| ----------------------------------------------------
|
|
102
102
|
|
|
|
103
103
|
= help: Create an index `CONCURRENTLY` and create the constraint using the index.
|
|
104
104
|
|
|
@@ -0,0 +1,4 @@
|
|
|
1
|
+
squawk_cli-2.9.0.data/scripts/squawk,sha256=yoE99ME4BJBhAXLfz-DYLqWu3RjPc4DTMtnogW21BO4,6881200
|
|
2
|
+
squawk_cli-2.9.0.dist-info/METADATA,sha256=7_NTQgI5Ndl0hjXrjZE8MDQL-wD-gNhR9mvlu1nFIFA,10441
|
|
3
|
+
squawk_cli-2.9.0.dist-info/WHEEL,sha256=WO7iD2gPn3bycRZocHMROV4zdxlG68K0VQMgqBCChus,101
|
|
4
|
+
squawk_cli-2.9.0.dist-info/RECORD,,
|
|
@@ -1,4 +0,0 @@
|
|
|
1
|
-
squawk_cli-2.8.0.data/scripts/squawk,sha256=S9_rLS-AcV0w4ZtvUL7hhZUZtWF91OPCpio4kBJ-mos,6792784
|
|
2
|
-
squawk_cli-2.8.0.dist-info/METADATA,sha256=BW1HEYoIveaavjvPqXQ5KIFjKgMWkJoiqPtPRAVFjrY,10441
|
|
3
|
-
squawk_cli-2.8.0.dist-info/WHEEL,sha256=WO7iD2gPn3bycRZocHMROV4zdxlG68K0VQMgqBCChus,101
|
|
4
|
-
squawk_cli-2.8.0.dist-info/RECORD,,
|
|
File without changes
|