You could follow the steps to set up a temporal table. If followed carefully then you should be able to get that column created fine to be able to feed into it.
One careful step is to either not activate temporal table before you migrate your data, or turn it off for the migration. IOW wait until after the migration before you run
ALTER TABLE rco ADD VERSIONING USE HISTORY TABLE rco_history;
There are some examples on how to turn off temporal support if you search Run SQL Scripts for temporal. Edit, Examples, Search from examples.
The reason you need to do that is the history table will not allow you to add rows until you turn it off.
DSPFD Command Input
File . . . . . . . . . . . . . . . . . . . : FILE RCO_HIST
Allow read operation . . . . . . . . . . . : Yes
Allow write operation . . . . . . . . . . . : No
Allow update operation . . . . . . . . . . : ALWUPD *NO
Allow delete operation . . . . . . . . . . : ALWDLT *YES

Ps: I'll be in Goshen tonight to watch my granddaughter play violin.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.