Re: [sqlite] Possible Input Parser Issue Inf How to convert SQL file into database when a column value is Inf?

2018-06-12 Thread Abroży Nieprzełoży
or .dump should produce output with 1e999 / -1e999 instead of Inf / -Inf 2018-06-13 1:11 GMT+02:00, Chris Brody : > On Tue, Jun 12, 2018 at 6:40 PM Richard Hipp wrote: >> [...] >> Maybe use 1e999 and -1e999 instead? > > I can confirm on SQLite versions 3.19.2 & 3.24.0: > > sqlite> select 1e999;

Re: [sqlite] Possible Input Parser Issue Inf How to convert SQL file into database when a column value is Inf?

2018-06-12 Thread Chris Brody
On Tue, Jun 12, 2018 at 6:40 PM Richard Hipp wrote: > [...] > Maybe use 1e999 and -1e999 instead? I can confirm on SQLite versions 3.19.2 & 3.24.0: sqlite> select 1e999; Inf sqlite> select -1e999; -Inf I wouldn't mind it if SQLite would be a little more symmetrical, i.e. output of .dump with

Re: [sqlite] Possible Input Parser Issue Inf How to convert SQL file into database when a column value is Inf?

2018-06-12 Thread Richard Hipp
On 6/12/18, Keith Medcalf wrote: > > The tip of trunk also does not parse "Inf" or "-Inf" floating point values Maybe use 1e999 and -1e999 instead? -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

[sqlite] Possible Input Parser Issue Inf How to convert SQL file into database when a column value is Inf?

2018-06-12 Thread Keith Medcalf
The tip of trunk also does not parse "Inf" or "-Inf" floating point values (eg: in an insert statement), but will produce Inf and -Inf output. The bind and column values interfaces however do handle the IEEE inf/-inf correctly. Is this a bug/oversight in the parser? sqlite> create table x(x