Add support for custom system time

[MarcoPignati]

Thanks for the extension. Very useful.
I am wondering if it is planned to support the possibility of having a custom system time to be sent for versioning together with the inserts or updates. Something similar to what is described here.

Currently our system stores changes and writes them (few seconds/minutes later) to the postgresql. For making sense of the data it would be useful to associate the timestamp at which the changes happened rather than relying on the system time (the transaction_timestamp() )

I was trying to use only add.periods and using the start_time and end_time as columns for the validity period and playing with add.periods_for_partion_views in order to send updates but it becomes a nightmare (I am not an expert of postgresql). From what I read I might need to implement triggers but I wouldn't like to redo what you already did (surely better than me).

In my understanding I cannot create an history table without first calling the periods.add_system_time_period and periods.add_system_versioning

Is there a workaround to avoid using the transaction_timestamp() but still leverage on all the work you did for versioning? Thanks!

[gaurav08suri]

@MarcoPignati - Did you find any workaround ?
@xocolatl - any workaround, you can suggest or are aware of ?

Thank you

[MarcoPignati]

no, I did not.