On 17 Feb 2014 at 17:01, Stephan Beal <sgb...@googlemail.com> wrote: > FWIW, i have seen a similar problem in a legacy app which uses latin1 > encoding in the DB. Latin1 doesn't always survive round-trip through PHP's > JSON APIs. My case was similar to yours, and we eventually determined that > the fields which got "lost" (set to null or empty values) were those which > came out of the latin1-encoded MySQL db containing invalid UTF8 characters > - the whole values were getting dropped upon transforming to JSON.
I'm not using JSON, and I've been careful to have everything in UTF8 throughout. I'm asking the user to send me the db, so I can look at it. But you make a good point. I said I've been careful, but the possibility I overlooked something related to that is not excluded. -- Cheers -- Tim
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
