You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i am also wondering, why oxtimestamp data type was changed to char(32) in november 2020 fbd1c2f
also the FCPO_REFERENCE was changed from char(32) to int(11) but if you are upgrading, then you already have rows with alphanumerical values there, so you cant simply import old data anymore.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
In the fcpayone_events.php the OXTIMESTAMP columns are created as CHAR(32):
oxid-6/core/fcpayone_events.php
Line 78 in dc2f45a
But the UPDATE statements change them to TIMESTAMP...
oxid-6/core/fcpayone_events.php
Line 655 in dc2f45a
and
oxid-6/core/fcpayone_events.php
Line 391 in dc2f45a
I think there is a migration missing for changing it to CHAR(32)?
btw: Why are you using CHAR(32) for this?
The text was updated successfully, but these errors were encountered: