Is there a difference in behaviour of DB2 on AS400 machines when it comes to handling not-nullable columns?
Someone just told me that if you insert a null value into a column with not null, on DB2 as400 it will work (sounds strange I know) , but will throw an error if Db2 is running on Windows.
I am going to verify this as soon as I get hold of the environment, still want to know if someone has ever heard of such a thing.
Closing Note: It was a schema that had changed over time... so the column had changed across releases, which led to the confusion.
I would say the answer is no. Here's a quick test I performed using interactive SQL (STRSQL) on V7R1:
CREATE TABLE QTEMP/TEST (F1 INT, F2 INT NOT NULL, F3 INT NOT NULL WITH DEFAULT);
INSERT INTO QTEMP/TEST (F1, F2, F3) VALUES(NULL, NULL, NULL);
Null values not allowed in column or variable F2.
INSERT INTO QTEMP/TEST (F1, F2, F3) VALUES(NULL, 0, NULL);
Null values not allowed in column or variable F3.