rspec/rules/S3618/plsql/rule.adoc

71 lines
1.2 KiB
Plaintext
Raw Normal View History

== Why is this an issue?
Any insert which omits a value for a `NOT NULL` column in a database table will be automatically rejected by the database unless a default value has been specified for the column.
2020-06-30 12:48:39 +02:00
include::../../../shared_content/plsql/data_dictionary.adoc[]
2021-02-02 15:02:10 +01:00
== How to fix it
2021-02-02 15:02:10 +01:00
Ensure that all `NOT NULL` columns have a value specified in the `INSERT` statement.
2020-06-30 12:48:39 +02:00
=== Code examples
2020-06-30 12:48:39 +02:00
Given the following table:
2022-02-04 17:28:24 +01:00
[source,sql]
2020-06-30 12:48:39 +02:00
----
CREATE TABLE MY_TABLE (
N1 NUMBER NOT NULL,
N2 VARCHAR2(50) NOT NULL,
N3 VARCHAR2(50) DEFAULT 'Default Value'
);
----
==== Noncompliant code example
[source,sql,diff-id=1,diff-type=noncompliant]
----
INSERT INTO MY_TABLE -- Noncompliant; N2 value omitted
(
N1
)
VALUES
(
1
)
2020-06-30 12:48:39 +02:00
----
=== Compliant solution
2020-06-30 12:48:39 +02:00
[source,sql,diff-id=1,diff-type=compliant]
2020-06-30 12:48:39 +02:00
----
INSERT INTO MY_TABLE -- Compliant; N3 has a default value
(
N1,
N2
)
VALUES
(
1,
'Paul'
)
2020-06-30 12:48:39 +02:00
----
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
include::../message.adoc[]
include::../highlighting.adoc[]
'''
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
endif::env-github,rspecator-view[]