Considering moving from a current database (that stores only facts which are believed to be true at the current time) to the temporal database (that can support for handling data involving time).
I communicate currently with the database with Entity Framework, but is it as easy to continue using Entity Framework with a temporal database as back-end? I haven't found much examples from the web where queries are run against such database.
If I get it right, you have not yet decided how you are going to implement the temporal aspect of your database. You could use an intrinsic way of the DBMS (eg triggers, logging, special mechanisms like Change Data Capture etc). But anyhow you would ensist on the relational model.
Therefore, the general answer would be that Entity Framework should have no problem playing with any relational model as long as there is a proper EF data provider for the specific DBMS.
However, regardless of your final decision on how you would implement the temporal aspect of the database, I would be really suspicious regarding performance and definetely build a load testing mechanism before making the transition.
Hope I helped!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With