Hello John, I feed everything to Sqlite in UTF-8. If it's coming from Windows, that means I have to do a UTF-16 to UTF-8 conversion. I know Sqlite has UTF-16 support but, I want things to be consistent across all OS's I work with. The less I have to think about things like this, the better.
C Thursday, October 16, 2014, 10:49:52 AM, you wrote: JM> On Thu, Oct 16, 2014 at 9:09 AM, Richard Hipp <d...@sqlite.org> wrote: >> On Thu, Oct 16, 2014 at 9:53 AM, John McKown <john.archie.mck...@gmail.com> >> wrote: >> >>> On Wed, Sep 24, 2014 at 9:46 PM, Richard Hipp <d...@sqlite.org> wrote: >>> > Please try the latest version of SQLite on trunk to see if that works >>> > better. Specifically, apply the patch at >>> > >>> > http://www.sqlite.org/src/vpatch?from=b2c89ef49cd1&to=ef30e0352b3d >>> > >>> > -- >>> > D. Richard Hipp >>> > d...@sqlite.org >>> >>> Unfortunately, the ASCII vs. EBCDIC issued _does_ make it >>> impossible to share a single SQLite data base file between z/OS and >>> other ASCII-based SQLite systems. >> >> >> If you store content in EBCDIC, it is retrieved in EBCDIC and if you store >> content in ASCII it is retrieved in ASCII, regardless of which platform you >> do the storing and retrieving on. I wonder if this is the right approach. >> Perhaps the zOS patch should be amended to simply transform EBCDIC->ASCII >> on input and ASCII->EBCDIC on output. >> JM> Hum, I'll need to look more closely at the code to see where this JM> would need to be implemented. As I indicated previously, making it JM> work on z/OS was so easy that I didn't need to really look closely at JM> the code itself. I basically compiled and it worked. And this was my JM> first attempt to port something to the z/OS environment, so I was not JM> very knowledgeable about it. I am somewhat more knowledgeable today JM> due to some other porting work that was somewhat more involved. I JM> guess that instead of saying ASCII<->EBCDIC, I need to say more JM> exactly ISO8859-1<->IBM-1047 since there are many "ASCII' and "EBCDIC" JM> code pages. Or does SQLite use UTF-8 internally? Hum, something else JM> to look into. I am not really that familiar with SQLite's internals. JM> Thanks for the thoughts. I appreciate your help. If I have more JM> questions, I guess that I would go over to the sqlite-dev forum. >> >> >>> I haven't looked closely enough at >>> the code to see if the big-endian (z/OS) vs. little-endian (Intel) >>> storage of integers would also be a problem. >>> >>> >> We do cross-platform database portability tests between x86, sparc, and >> PPC, to verify that big-endian vs little-endian is not a factor. JM> Thanks for telling me that. I won't worry about it again. >> >> -- >> D. Richard Hipp >> d...@sqlite.org >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Teg mailto:t...@djii.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
