View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000621 | OXID eShop (all versions) | 4.07. Source code, Test | public | 2009-02-23 14:47 | 2012-12-10 13:45 |
| Reporter | tjungcl | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.0.1.0 revision 15990 | ||||
| Fixed in Version | 4.1.0 revision 17976 | ||||
| Summary | 0000621: OXVARNAME Field Type VARCHAR(32) a bit stingy | ||||
| Description | Even the OXTEMPLATE field, which contains only a filename without path, is four times bigger. OXARTNUM is even varchar(255)... A name like "Flamingo // Guest towels, set of 2" cant be imported, which would limit our applicability of oxid eshop very much. | ||||
| Tags | No tags attached. | ||||
| Theme | |||||
| Browser | All | ||||
| PHP Version | 5.2.6 | ||||
| Database Version | 5.0.33 | ||||
|
|
As such requests can be setuped easily on local DB according to needs, it's not a Blocker bug. But for convenience, this will be fixed in future releases. |
|
|
Oh, i wasnt aware that i can change the data-modell without risking to loose update-ability. I thought, every eshop-version-update could change the fieldtype back to varchar(32) which would delete half of my data. |
|
|
For bugfix - extend OXVARNAME to VARCHAR(128) |
|
|
OXVARNAME/OXVARSELECT fields length increased to 255 chars |
