Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012691Openbravo ERPA. Platformpublic2010-03-15 22:252010-05-18 12:12
Reporteriperdomo 
Assigned Toshuehner 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS20OS Version2.6.30-gentoo-r5
Product Version 
Target Version2.50MP17Fixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0012691: Export dataset should fail with non ASCII characters in dataset name
DescriptionA 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.
Steps To Reproduce
Proposed Solution* Export database process should fail if the dataset contains non ASCII characters
Additional Information
TagsNo tags attached.
Relationships
related to defect 00120502.50MP14 closed shuehner Dataset names should only use ascii characters 
related to feature request 0013275 new Triage Platform Base Invalid dataset name should be checked when entering it (via a callout) instead of only on export 
Attached Filespng dataset1.png (177,033) 2010-03-15 22:26
https://issues.openbravo.com/file_download.php?file_id=2346&type=bug
png

txt dataset-list.txt (316) 2010-03-15 22:27
https://issues.openbravo.com/file_download.php?file_id=2347&type=bug
Issue History
Date ModifiedUsernameFieldChange
2010-03-15 22:25iperdomoNew Issue
2010-03-15 22:25iperdomoAssigned To => shuehner
2010-03-15 22:25iperdomoOBNetwork customer => No
2010-03-15 22:26iperdomoFile Added: dataset1.png
2010-03-15 22:27iperdomoFile Added: dataset-list.txt
2010-03-15 22:28iperdomoRelationship addedrelated to 0012050
2010-03-15 22:28iperdomoStatusnew => scheduled
2010-03-15 22:28iperdomofix_in_branch => pi
2010-05-10 17:29shuehnerRelationship addedrelated to 0013275
2010-05-10 17:31shuehnerNote Added: 0027110
2010-05-10 17:31shuehnerStatusscheduled => closed
2010-05-10 17:31shuehnerResolutionopen => no change required
2010-05-11 00:00anonymoussf_bug_id0 => 2999638
2010-05-18 12:12gorka_gilTarget Version2.50MP15 => 2.50MP17

Notes
(0027110)
shuehner   
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