Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0027994
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Retail Modules] Web POSmajoralways2014-10-27 21:432014-12-15 13:04
ReporterjecharriView Statuspublic 
Assigned Tomarvintm 
PrioritynormalResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0027994: Web POS does not search properly with strange characters (take into account all of them) in the product name

DescriptionWeb POS does not search properly with strange characters (take into account all of them) in the product name
Steps To Reproduce-Change a product name to Roüet

-Go to Web POS and try to find by Rouet

Verify that Web POS does not search the product.
Proposed SolutionIt should work with all strange characters. For example french strange characters
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0071696)
mtaal (manager)
2014-11-17 12:00

Copy of email discussion:
Since WebSQL is built on top of SQLite, I've been doing some research about Unicode and SQLite.
SQLite (and therefore WebSQL) does support Unicode (all data is saved in Unicode formatting), but the querying is a bit limited. Querying ignoring accents/diacritical marks is not supported by SQLite. I've done some tests and the Chrome Dev console returns the following:
> select 'u' like 'U' => True
> select 'ü' like 'Ü' => True
> select 'u' like 'ü' => False

Proposed solutions include creating custom collations to replace the behaviour of the like() function or creating a "normalized" column to execute queries against it.
Since we can't control the implementation of WebSQL inside the Web browser, I think adding new collations would be very difficult if not impossible. Adding a new normalized column would work but this brings me back to the questions involving the character set we should support (e.g. if we should support ø, æ,...). Anyway, the downsides of creating a normalized column are:
a) We would only be supporting diacritics-free quering for the m_product table, instead of diacritics-free quering for the entire database.
b) We would need to create the normalizing function and include all the translations we'd like to support.

- Issue History
Date Modified Username Field Change
2014-10-27 21:43 jecharri New Issue
2014-10-27 21:43 jecharri Assigned To => marvintm
2014-10-27 21:43 jecharri Resolution time => 1417388400
2014-10-27 21:43 jecharri Triggers an Emergency Pack => No
2014-10-27 21:50 jecharri Summary Web POS does not search properly with strange characters in the product name => Web POS does not search properly with strange characters (take into account all of them) in the product name
2014-10-27 21:50 jecharri Description Updated View Revisions
2014-10-27 21:50 jecharri Proposed Solution updated
2014-11-13 09:26 mtaal Assigned To marvintm => aaroncalero
2014-11-14 14:35 mario_castello Assigned To aaroncalero => mario_castello
2014-11-14 14:35 mario_castello Status new => scheduled
2014-11-14 14:35 mario_castello fix_in_branch => pi
2014-11-14 18:33 mtaal Assigned To mario_castello => aaroncalero
2014-11-17 12:00 mtaal Note Added: 0071696
2014-11-30 11:25 mtaal Assigned To aaroncalero => szapata
2014-12-08 16:30 jecharri fix_in_branch pi =>
2014-12-15 13:04 mtaal Assigned To szapata => marvintm
2014-12-15 13:04 mtaal Type defect => design defect


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker