On Mon, Dec 12, 2016 at 9:30 PM, Bradford Larsen wrote:
> An alternative possibility would be to revert to the pre-3.11 tokenizer on
> EBCDIC systems. If I recall, the old tokenizer used a big switch statement
> with character literals instead of the 'aiClass' table. I
>
> On Sun, Dec 11, 2016 at 20:42 Richard Hipp wrote:
>
> SQLite only uses the "[" character as a compatibility quoting
>
> mechanism for SQL Server. Maybe the solution is for [...] quoting to
>
> simply not work on EBCDIC systems?
>
>
>
> --
>
> D. Richard Hipp
>
>
SQLite only uses the "[" character as a compatibility quoting
mechanism for SQL Server. Maybe the solution is for [...] quoting to
simply not work on EBCDIC systems?
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
On Dec 11, 2016, at 4:57 PM, Richard Hipp wrote:
> I agree with most of your changes. But I wonder about moving the
> QUOTE2 (the '[' character) value from code 0xba over to 0xad.
> According to EBCDIC chart at https://en.wikipedia.org/wiki/EBCDIC the
> '[' character should be
> On Dec 11, 2016, at 7:57 PM, Richard Hipp wrote:
>
> On 12/11/16, Bradford Larsen wrote:
>
>> #endif
>> #ifdef SQLITE_EBCDIC
>> /* x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xa xb xc xd xe xf */
>> /* 0x */ 27, 27, 27, 27, 27, 7, 27, 27,
On 12/11/16, Bradford Larsen wrote:
> #endif
> #ifdef SQLITE_EBCDIC
> /* x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xa xb xc xd xe xf */
> /* 0x */ 27, 27, 27, 27, 27, 7, 27, 27, 27, 27, 27, 27, 7, 7, 27, 27,
> /* 1x */ 27, 27, 27, 27, 27, 27, 27, 27, 27,
6 matches
Mail list logo