Re: [sqlite] Bug report + fix: SQLite 3.11+ broken on EBCDIC systems

> > 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 > >

Re: [sqlite] Bug report + fix: SQLite 3.11+ broken on EBCDIC systems

> On Dec 11, 2016, at 7:57 PM, Richard Hipp <d...@sqlite.org> wrote: > > On 12/11/16, Bradford Larsen <brad.lar...@gmail.com> wrote: > >> #endif >> #ifdef SQLITE_EBCDIC >> /* x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xa xb xc xd xe xf */ &g

[sqlite] Bug report + fix: SQLite 3.11+ broken on EBCDIC systems

SQLite has built-in support for EBCDIC-based systems, but I discovered that it’s been broken since 3.11.0. If you have an EBCDIC-based system, you can see the brokenness by firing up `sqlite` and trying the `.schema` metacommand – you’ll get an obscure error. In detail, in February 2016,

[sqlite] SQLite 3.11+ broken on EBCDIC systems (includes patch)

SQLite has built-in support for EBCDIC-based systems, but I discovered that it’s been broken since 3.11.0. In particular, in February 2016, several changes were made to the SQL tokenizer for performance to use a character lookup table instead of a switch statement based on character literals