search

ayier1 / worktime

Automatically exported from code.google.com/p/worktime
0 stars 0 forks source link

Sync fails with special characters #214

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.trying to sync
2.
3.

What is the expected output?

What do you see instead?

What version of the product are you using (check the about screen for thelatest
version or version number)?
latest

Please provide any additional information below.

Original issue reported on code.google.com by shay.na...@mail.huji.ac.il on 2 Apr 2013 at 8:51

GoogleCodeExporter commented 8 years ago 
Hey what exactly is going wrong?
Can you tell me what is displayed in the account profile screen or even in the 
list of sync history?

Additionally it would be nice and much easier for me to test if you could just 
send me a backup file. Therefore you go into Preferences -> Backup & Restore. 
Then create a backup and send that backup file to me 
(dirkvranckaert@gmail.com). Do not attach it to this issue because that would 
make your data available to the rest of the world!

Original comment by dirkvran...@gmail.com on 3 Apr 2013 at 8:43

GoogleCodeExporter commented 8 years ago 
Received Email:

hi,

i've attached 2 backups 1 (before syncing) and 2 (after syncing).
the last report from the sync is: currupttaskdataexception
I think it's due to the fact that I use Hebrew characters and the encoding on 
the server is set differently.
I'd love to help...

shay

Will try to reproduce!

Original comment by dirkvran...@gmail.com on 4 Apr 2013 at 6:26

GoogleCodeExporter commented 8 years ago 
The main problem has been solved in a previous issue, however due to the issue 
back then there are two tasks for one project with the same name. Will resolve 
this individually.

However there is one more problem querying special charachters on the 
device-local database.
We should use OrmLite's SelectArg 
(http://ormlite.com/javadoc/ormlite-core/com/j256/ormlite/stmt/SelectArg.html) 
to resolve this issue and to make the entire DAO layout SQL inject proof!

Original comment by dirkvran...@gmail.com on 4 Apr 2013 at 8:33

GoogleCodeExporter commented 8 years ago

Original comment by dirkvran...@gmail.com on 4 Apr 2013 at 10:48