Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Temporal Tables in a sensible manner #45

Open
ftrotter opened this issue Sep 9, 2019 · 1 comment
Open

Support Temporal Tables in a sensible manner #45

ftrotter opened this issue Sep 9, 2019 · 1 comment

Comments

@ftrotter
Copy link
Contributor

ftrotter commented Sep 9, 2019

Currently, DURC assumes that created_at and updated_at should be DATETIME types.

DURC should be smart enough to detect and work with MariaDB temporal tables

https://mariadb.com/kb/en/library/temporal-data-tables/

@ftrotter ftrotter added 1.0 requirement Things we need in initial release enhancement labels Sep 9, 2019
@ftrotter
Copy link
Contributor Author

ftrotter commented Dec 8, 2019

I have confirmed that when you use the temporal tables, without creating the explicit variables, that DURC works just fine. Since a table with temporal tables can look just like one that does not, the real feature is going to be checking every MariaDB table to see if it has a "history" and then, when it does, provide some additional version report... (but do nothing for regular tables).

Closing this as a 1.0 consideration

@ftrotter ftrotter removed the 1.0 requirement Things we need in initial release label Dec 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant