Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0012691 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] A. Platform | major | always | 2010-03-15 22:25 | 2010-05-18 12:12 | |||
| Reporter | iperdomo | View Status | public | |||||
| Assigned To | shuehner | |||||||
| Priority | urgent | Resolution | no change required | Fixed in Version | ||||
| Status | closed | Fix in branch | pi | Fixed in SCM revision | ||||
| Projection | none | ETA | none | Target Version | 2.50MP17 | |||
| OS | Linux 32 bit | Database | PostgreSQL | Java version | 1.6.0_15 | |||
| OS Version | 2.6.30-gentoo-r5 | Database version | 8.3.8 | Ant version | 1.7.1 | |||
| Product Version | SCM revision | |||||||
| Merge Request Status | ||||||||
| Review Assigned To | ||||||||
| OBNetwork customer | No | |||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Support ticket | ||||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0012691: Export dataset should fail with non ASCII characters in dataset name | |||||||
| Description | A validation was added to the package.module task, but you can export a dataset with non ASCII chars in its filename directly from the Openbravo UI. | |||||||
| Proposed Solution | * Export database process should fail if the dataset contains non ASCII characters | |||||||
| Tags | No tags attached. | |||||||
| Attached Files |  dataset1.png [^] (177,033 bytes) 2010-03-15 22:26
 dataset-list.txt [^] (316 bytes) 2010-03-15 22:27 [Show Content]
| |||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||||||||
|
|||||||||||||||
 Relationships |
|
Notes |
|
|
(0027110) shuehner (administrator) 2010-05-10 17:31 |
After discussion with reporter. Adding a validation there does not really improve the developer experience. Instead adding a callout to warn about illegal dataset names when entering them would improve the process. This other idea is not logged as 13275. -> Closing this |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-03-15 22:25 | iperdomo | New Issue | |
| 2010-03-15 22:25 | iperdomo | Assigned To | => shuehner |
| 2010-03-15 22:25 | iperdomo | OBNetwork customer | => No |
| 2010-03-15 22:26 | iperdomo | File Added: dataset1.png | |
| 2010-03-15 22:27 | iperdomo | File Added: dataset-list.txt | |
| 2010-03-15 22:28 | iperdomo | Relationship added | related to 0012050 |
| 2010-03-15 22:28 | iperdomo | Status | new => scheduled |
| 2010-03-15 22:28 | iperdomo | fix_in_branch | => pi |
| 2010-05-10 17:29 | shuehner | Relationship added | related to 0013275 |
| 2010-05-10 17:31 | shuehner | Note Added: 0027110 | |
| 2010-05-10 17:31 | shuehner | Status | scheduled => closed |
| 2010-05-10 17:31 | shuehner | Resolution | open => no change required |
| 2010-05-11 00:00 | anonymous | sf_bug_id | 0 => 2999638 |
| 2010-05-18 12:12 | gorka_gil | Target Version | 2.50MP15 => 2.50MP17 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |