Demo data and testing fixture data fails: invalid datetime format?
Hi there,
we recently updated our Spryker project, in specific we updated spryker/propel-orm and hence propel/propel from 2.0.0-beta1 to 2.0.0-beta2.
Now all our demo data and testing fixture data fails where we have dates like '2050-12-31'. Propel tells us, that this is an invalid datetime format. '2037-12-31' works however.
Anybody seen that and has a clue what is causing this?
Best Answer
-
Yes, valid dates are now needed. Databuilders should have gotten Updates here, see RG overview of modules needed.
0
Answers
-
Yes, valid dates are now needed. Databuilders should have gotten Updates here, see RG overview of modules needed.
0 -
But why is 2050-12-31 invalid?
0 -
Out of range of timestamp afaik
0 -
Bloody propel
0 -
Bloody (invalid) timestamps in use π 32bit range.
0 -
https://en.wikipedia.org/wiki/Year_2038_problem β¦ the end is near β¦
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 79 Spryker News
- 948 Developer Corner
- 806 Spryker Development
- 91 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 33 Product & Business Questions
- 69 Spryker Safari Questions
- 50 Random