View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004893 | OXID eShop (all versions) | 4.01. Database handling | public | 2013-02-04 10:41 | 2013-02-04 12:45 |
| Reporter | JaroslavHerber | Assigned To | |||
| Priority | high | Severity | tweak | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Summary | 0004893: Database: oxarticles.OXPARENTID should be varchar, not char(32) | ||||
| Description | oxarticles.OXPARENTID can also be empty, so char(32) may use more storage than varchar. | ||||
| Tags | No tags attached. | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
|
|
After changing oxarticles.OXPARENTID to varchar the size of our oxarticles-table went down from 58.3 MiB to 42.3 MiB |
|
|
yes it saves memory, but lose in speed (http://dba.stackexchange.com/questions/2640/what-is-the-performance-impact-of-using-char-vs-varchar-on-a-fixed-size-field) of course the pest way is to use integer, in near future we will go this way. |
