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

🚀 Feature: Allow value for createdAt & updatedAt on create/update Document #285

Open
2 tasks done
fliitor opened this issue Jun 23, 2023 · 3 comments · May be fixed by #286
Open
2 tasks done

🚀 Feature: Allow value for createdAt & updatedAt on create/update Document #285

fliitor opened this issue Jun 23, 2023 · 3 comments · May be fixed by #286
Assignees
Labels
enhancement New feature or request

Comments

@fliitor
Copy link

fliitor commented Jun 23, 2023

🔖 Feature description

This fields auto generate on insert / update

It can be usefull to force them via data like

{
...otherFields,
"$createdAt": "string or timestamp"
}

🎤 Pitch

In case of migration for others platform, without this we need to inject data directly on MariaDB, or we'll loose this information or if we simply need to change it for any other reason

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

fliitor added a commit to fliitor/database that referenced this issue Jun 23, 2023
@fliitor
Copy link
Author

fliitor commented Jun 23, 2023

I let it autogenerate on update. There are bound to be cases where it's necessary, but having it on hand at the time of creation already solves a lot of needs.

TODO if PR accepted, modify documentation to replicate this change

@joeyouss
Copy link

Thank you for your PR.

Our team will review it ASAP.

@fliitor
Copy link
Author

fliitor commented Jun 3, 2024

This can be close because it's already implemented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants