On 10/21/10 11:22 AM, Ed Leafe wrote: > On Oct 21, 2010, at 1:37 PM, John Fabiani wrote: > >> Yes I understand what you have said. I'm looking at it in a much more basic >> way. So let me say it in a different way. If the app is setup to use utf8 >> and the data is not. What happens? I believe Paul's question is should the >> app follow the database encoding or be set in the app. So I'd like to know >> what happens when there are two different encodings. > > > As Paul mentioned, encoding/decoding should only happen at the > interface between the program and its storage. If SQLite can only use utf8, > then communication to/from SQLite should be be using utf8. If SQLite can use > any encoding, then it should use the app's preferences.
Actually, what I was saying was that Dabo's handling of fields to/from the database - whatever database - should be in the encoding set in the database. The encoding set in the database should trump the App's encoding. So, if the SQLite database is UTF-16, and Dabo's encoding is UTF-8, then when we query the database we need to decode using UTF-16, and when we save back to that database we need to encode with UTF-16 too. I'm fuzzy on what we should do when working with the fields at the biz and UI layer. Do we encode to UTF-8 (or whatever dabo.defaultEncoding is) for display in a text field, for example? Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
