Re: [sqlite] Possible bug with union and join.

2016-12-25 Thread Adrian Stachlewski
Fortunately names of columns are much more transparent and documented in our internal specification. 'Id' was created only for example, but thanks for advice :) Adrian 2016-12-25 13:44 GMT+01:00 Simon Slavin : > > On 23 Dec 2016, at 4:55pm, Adrian Stachlewski > wrote: &g

Re: [sqlite] Possible bug with union and join.

2016-12-25 Thread Adrian Stachlewski
As I wrote in my previous message, I was quite sure, that comparing text columns and integer columns should work. Hopefully in other cases fields which are compared are same types. Adrian 2016-12-23 13:00 GMT+01:00 Simon Slavin : > > On 22 Dec 2016, at 5:55pm, Adrian Stachlewski > wrote: &

Re: [sqlite] Possible bug with union and join.

2016-12-23 Thread Adrian Stachlewski
ext and integer columns is safe. -- Adrian Stachlewski 2016-12-22 16:06 GMT+01:00 Richard Hipp : > Adrian: > > String are not equal to numbers. You should not expect that '4'==4. > Yes, I know that SQLite will sometimes do this. The complex type > coercion rules were

[sqlite] Possible bug with union and join.

2016-12-22 Thread Adrian Stachlewski
id_map.id AS TEXT) everything it's working fine. Unfortunately this workaround makes no sense for me, as long as SELECT CAST(1 AS TEXT) = CAST(1 AS INTEGER); gives True. SQLite versions: - 3.13.0 - 3.15.2 - pre-release snapshot OS: Ubuntu 16.04.1 LTS with 4.4.0-57-generic I hope

[sqlite] Possible bug with union and join.

2016-12-22 Thread Adrian Stachlewski
id_map.id AS TEXT) everything it's working fine. Unfortunately this workaround makes no sense for me, as long as SELECT CAST(1 AS TEXT) = CAST(1 AS INTEGER); gives True. SQLite versions: - 3.13.0 - 3.15.2 - pre-release snapshot OS: Ubuntu 16.04.1 LTS with 4.4.0-57-generic I hope