Description Chris Khoun 2012-08-09 11:50:06 EDT

Created attachment 219717 [details]
Code fix for this problem on top of DTP 1.8.2

I checked the master branch of DTP to make sure this bug wasn't already fixed in the latest code base. I have attached a patch that fixes this issue. The patch is based on DTP 1.8.2.

Repro Steps.
1. Open any product that utilizes DTP 1.8.2 such as RAD 8.5.
2. Open the Data perspective and connect to a DB2 database through the Data Source Explorer. (I used a local DB2 LUW v10.1 but any os/version should reproduce this)
3. Select "New SQL Script" and create a new table with the following query.

CREATE TABLE DB2ADMIN.TESTTABLE1 (NAME1  VARCHAR(20) NOT NULL,
				  NAME2  VARCHAR(20) NOT NULL WITH DEFAULT,
				  NUM1   INTEGER NOT NULL WITH DEFAULT)

3. Expand the database tree in the Data Source Explorer to your newly created table.
4. Right click the table -> Data -> Edit
5. Enter a value into the NAME1 column (don't put anything in the other columns)
6. Right click -> Save   this will trigger the error.

The generated insert is as follows (which is wrong)
insert into "DB2ADMIN"."TESTTABLE1" ("NAME1", "NAME2", "NUM1") values('CKTEST1', null, null)
It should instead actually be
insert into "DB2ADMIN"."TESTTABLE1" ("NAME1") values('CKTEST1')