U+2028 (LINE SEPARATOR) in index files appears to cause a fatal database error on resolution of a query #41
Comments
|
If '\n' is a newline char it should be stripped out of names and titles. They are not needed and may cause problems elsewhere.
… On Jun 26, 2017, at 12:41 PM, Asa Hardcastle ***@***.***> wrote:
This issue is likely related to this issue:
storesafe/cordova-sqlite-storage#147 <storesafe/cordova-sqlite-storage#147>
It appears that whenever a query returns results that contain one of the many indices where the key has the character combination '\n' -- a crash happens. Here is an example.
"གྲགས་པ་རྒྱལ\nམཚན། གསུང་འབུམ":["W3GSP297"]
The temporary fix is to remove all of these from the index files.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#41>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADYNFq2MUsb4JMCeXaBB_WTS91A4lDQIks5sH-07gaJpZM4OFoDP>.
|
|
This didn't solve the problem with "དོན་ག" and "དོན་གྲུབ་" though... |
|
NT: did the app reimport when you launched the new version? You may need to uninstall it fully from your phone and try again. It tested fine on my iPhone. :( |
|
I have now tested this on my android phone (S5) from the Play Store install, and the problem is no longer there with the latest release (last week). Can you confirm, @ngawangtrinley ? |
subsystem7
changed the title
|
Just FYI: Here are the entries in the indexes that containe the unicode line separator: [Log] possible bad data - found LINE SEPARATOR U+2028 [Log] possible bad data - found LINE SEPARATOR U+2028 [Log] possible bad data - found LINE SEPARATOR U+2028 [Log] possible bad data - found LINE SEPARATOR U+2028 [Log] possible bad data - found LINE SEPARATOR U+2028 |
|
I added code that removes U+2028 and U+2029 if they appear in the key. |
This issue is likely related to this issue:
storesafe/cordova-sqlite-storage#147
It appears that whenever a query returns results that contain one of the many indices where the key has the character combination '\n' -- a crash happens. Here is an example.
"གྲགས་པ་རྒྱལ\nམཚན། གསུང་འབུམ":["W3GSP297"]
The temporary fix is to remove all of these from the index files.
The text was updated successfully, but these errors were encountered: