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

createdAt field gets overwritten when creating new version #186

Open
tavsec opened this issue Mar 4, 2024 · 0 comments
Open

createdAt field gets overwritten when creating new version #186

tavsec opened this issue Mar 4, 2024 · 0 comments

Comments

@tavsec
Copy link

tavsec commented Mar 4, 2024

Bug report

Describe the bug

When creating new version of versioned model, the createdAt field is also the same as updatedAt date. I think that the createdAt field should also stay the same.

Steps to reproduce the behavior

  1. Create versioned model
  2. Create new entry for this model and save it
  3. Check createdAt date
  4. Update this entry
  5. Check new createdAt date. It is updated, but it shouldn't

Expected behavior

createdAt date should stay the same for all of the versioned (timestamp, when the entry was first created).

System

  • Node.js version: v18
  • NPM version: 9.5
  • Strapi version: v4
  • Database: mysql
  • Operating system: macOS/Ubuntu
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant