|
Having thought this through a bit, the CURRENT_TIMESTAMP should come from the machine executing the cpimport / API. This will be true for TZ as well when we support it. We should not assume that the PMs have the same clock or TZ as the UM. This means we will need them to look for "CURRENT_TIMESTAMP" in the default value in the system catalogue and act appropriately.
Depending on how the storage engine API sends this data we may also need a special message from the UM to fill this in.
We also need to support "ON UPDATE CURRENT_TIMESTAMP" which can also probably go into the default value of the system catalogue (another flag column is also possible, but would be harder for compatibility, maybe make the autoincrement column a bitmask?). This for now would only need support for MariaDB queries.
|