Changes between Initial Version and Version 1 of Ticket #588, comment 7


Ignore:
Timestamp:
Jan 17, 2014, 3:59:37 PM (10 years ago)
Author:
Piero Campalani

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #588, comment 7

    initial v1  
    99Despite this, it seems that the `--output` argument is ignored when no encoding is specified in the query and the result is a scalar: that is, the above query gives `10` and not "`0A` if I set `--output hex`. As well for instance `select avg_cell(pow((c) [3,52:54,151], 2.0)) from eobstest as c` returns a `string` (1.69838e+06) output though it is set to hex.
    1010Maybe this deserves a separate ticket.
    11 
    12 I'll add an other related use case, which I usually refer to as ''crazy floats'' bug:
    13 
    14 {{{
    15 select pow((c) [3,52:54,151], 2.0) from eobstest AS c"
    16   Result object 1: {1.21661e+06,1.68221e+06,2.19632e+06}
    17 
    18 select dbinfo(c) from eobstest as c | grep baseType
    19  "baseType": "marray <short>",
    20 }}}
    21 
    22 This is related to the fact that the original values `{-1103,-1297,-1482}` go short-overflow when squared. This happens as well if you replace the subsetting on the collection with a constant number.