on 12-18-2015 7:56 AM
When trying to reverse engineer from DB2 11 on ZOS all identity columns and timestamp columns with 'FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP' are not handled correctly. These attributes seems to be ignored by Powerdesigner.
This is how identity columns look like after beeing reverse engineered:
Source column defined like this:
id integer not null generated by default as identity (cycle)
And columns defined like this:
last_login timestamp not null generated by default for each row on update as row change timestamp
is looking like this after after beeing reverse engineered (ordinary timestamp column):
Any suggestions how to get this to work properly?
Arild
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is how my table is defined in DB2 11 for z:
CREATE TABLE TESTVIP.ROITASKS (
id integer not null generated by default as identity (cycle),
investor_Id char(11) not null,
created timestamp not null with default,
from_Date date,
to_Date date
) VOLATILE
IN DVIP.SVIP16
;
And this is how it turns out in Powerdesigner after reverse engineering:
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.