Closed suricactus closed 8 years ago
Hello @suricactus,
What you are trying to achieve is called application-time period tables and is not currently supported by the extension. In fact, you do not even need an extension to implement them since the application-time period is controlled by the application, not by the system (that is why the other type of temporal tables is called system-time period tables).
I have been thinking about implementing application-time period tables, but I am not sure if I will find enough time to tackle it. The most painful part is versioned FKs and PKs.
Thank you! Sorry I misunderstood the purpose of your extension. I just thought I might be reinventing the wheel. Hope you have enough time to implement another plugin for application-time period tables one day. Best wishes!
Sorry, I might be totally misunderstanding but I wondered ... it seems in this case these old historical rows have no history yet, then you might really be simply wanting the sys_period start timestamp to match some prior timestamp?
It seems to me that if you don't have the trigger active you can update that start timestamp. So you could only create the trigger after the start timestamps are what you want.
Sorry, I just thought I'd add that in case you really are looking for that option.
Hello. I found your extension and at first glance it seemed to be exactly what I need.
But I have a trouble when I need to add truly historical rows (that have been active decades ago). How I can set sys_period to be timestamp in the past?
Here is the proble:
This is my schema: