I think so, or, use a view which omits the TIMESTAMP
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Anderson, Kurt
Sent: Friday, March 15, 2013 8:55 AM
To: 'Midrange Systems Technical Discussion'
Subject: SQL Table with ROW CHANGE TIMESTAMP
Just got back from the WMCPA conference and I'm using today to apply some of the learning that occurred earlier this week.
One thing I learned about was being able to have my SQL table automatically set the last change timestamp field w/o me doing it.
Example: ChgDate TIMESTAMP FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP NOT NULL,
I added some records via DBU and saw that this worked great.
Unfortunately this seems to be de-simplifying the embedded SQL in my program.
I had Insert into BillAgentP Values(:ds_Insert); Where ds_Insert is a Qualified DS defined like the file. But now that doesn't work b/c it doesn't like that I'm updating ChgDate. Is my only recourse to list out all the fields except for ChgDate?
I'm at IBM i 7.1
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.