View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005581 | OXID eShop (all versions) | 4.01. Database handling | public | 2013-12-18 10:51 | 2015-05-04 14:40 |
| Reporter | mpienkny | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | duplicate | ||
| Summary | 0005581: Failure in database query should be reported, not just ignored | ||||
| Description | If any SQL statement fails (e.g. different collations on columns) this must be examined, and not just go on with empty record set. | ||||
| Steps To Reproduce | This is just an _example_ - this topic is anywhere accessing the database Database is MySQL 5.5 - collation of database is utf8_general_ci Column oxarticles.oxefichecksum has collation latin1_general_ci When eFire search for new products in where-clause is something like "oxefichecksum != MD5(...." - this crashes silently and so no new or updated products are sent to eFire anymore. | ||||
| Tags | Collation, Database | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
| related to | 0005582 | resolved | mantas.vaitkunas | There is no check for errors in database queries when production mode turned on. This leads to unpredictable Shop state. |
