Problem with database default values (OXTIMESTAMP)

PAYONE-GmbH / oxid-6

The PAYONE Oxid 6 payment module

https://www.payone.com/

MIT License

5 stars 26 forks source link

Problem with database default values (OXTIMESTAMP) #162

Closed hkreuter closed 3 years ago

hkreuter commented 4 years ago

When running OXID eshop 6.2 compilation tests (means running tests with compilation modules installed, tests are run for shop and for each module) there are broken tests for shop and multiple modules when the PayOne module is around. Looks like issues are caused by incorrect database default values for example

OXTIMESTAMP CHAR(32) COLLATE latin1_general_ci NOT NULL DEFAULT '',

Could you please have a look and fix this? If you need more information, feel free to contact me :)

T-Kuchel commented 4 years ago

Hi @hkreuter ,

we will check that and hopefully solve that issue.

Greetings from Kiel Timo

stale[bot] commented 4 years ago

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.

hreinberger commented 4 years ago

This should also be fixed by #172

stale[bot] commented 4 years ago

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.

swinde commented 3 years ago

I can confirm this error for version 1.4.0

log_fpo_1.4.txt

stale[bot] commented 3 years ago

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.