View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005784 | OXID eShop (all versions) | 4.01. Database handling | public | 2014-06-03 14:28 | 2014-06-10 15:01 |
Reporter | dreibein | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Platform | Linux | OS | Turboleo | OS Version | 3.2.0-63-generic |
Product Version | 4.8.1 / 5.1.1 | ||||
Target Version | 4.9.0_5.2.0_beta1 | Fixed in Version | 4.8.7 / 5.1.7 | ||
Summary | 0005784: Wrong Data Format for SQL Update of Date field | ||||
Description | e.g. in the myorder.php the value of the oxbilldate is set as d.m.Y, the SQL defintion of it is Y-m-d. If the SQL Server doesn't correct it, it leads to wrong values of all dates stored in the Database. | ||||
Tags | No tags attached. | ||||
Theme | Azure | ||||
Browser | All | ||||
PHP Version | any | ||||
Database Version | any | ||||
|
Why would you set "d.m.Y", if its not the right date-format? from the setup/sql/database.sql-file: CREATE TABLE `oxorder` ( -- ... `OXBILLDATE` date NOT NULL default '0000-00-00' COMMENT 'Invoice sent date', -- ... `OXSENDDATE` datetime NOT NULL default '0000-00-00 00:00:00' COMMENT 'Order shipping date', -- ... regarding the documentation the sql-setup is correct http://dev.mysql.com/doc/refman/5.5/en/datetime.html "The DATE type is used for values with a date part but no time part. MySQL retrieves and displays DATE values in 'YYYY-MM-DD' format." Even oxutilsdate::formatDBDate is using "Y-m-d" |
|
changed format |