atsd_entity column type is varchar for numeric type about atsd-jdbc HOT 14 CLOSED

@rodionos
Please, try the following query:

SELECT tags.symbol, tags.class_code, CAST(tags.lot AS integer) FROM atsd_entity WHERE tags.symbol = 'LKOH' limit 1

Without CAST, AS assigns a column alias

from atsd-jdbc.

Indeed, my mistake. Related issue, with getString returning the value with fractions:

CAST(tags.lot AS INTEGER) AS lot

rs.getString(3) - returns 1.0

from atsd-jdbc.

SELECT datetime, trade_num, price, quantity, side FROM atsd_trade

getString(1) returns truncated time
2021-04-08 07:00:03

from atsd-jdbc.

Is there a way to get precise trade datetime, including microseconds?

from atsd-jdbc.

Indeed, my mistake. Related issue, with getString returning the value with fractions:

CAST(tags.lot AS INTEGER) AS lot

rs.getString(3) - returns 1.0

I will fix it in ATSD by returning correct datatype in metadata. Now double is returned in any case.

BTW, shouldn't we support all known numeric datatypes in CAST expression? Currently only number, integer, float are supported.

from atsd-jdbc.

Is there a way to get precise trade datetime, including microseconds?

Could you try with latest version 1.4.9, please? It should be available in Maven

from atsd-jdbc.

Only 1.4.8 is available on mavencentral:

<dependency>
    <groupId>com.axibase</groupId>
    <artifactId>atsd-jdbc</artifactId>
    <version>1.4.8</version>
</dependency>

from atsd-jdbc.

https://mvnrepository.com/artifact/com.axibase/atsd-jdbc - here only 1.4.8 is listed

from atsd-jdbc.

https://mvnrepository.com/artifact/com.axibase/atsd-jdbc - here only 1.4.8 is listed

Index is not updated yet, but the jar should be available
https://search.maven.org/artifact/com.axibase/atsd-jdbc/1.4.9/jar

from atsd-jdbc.

datetime works ok with the 1.4.9 downloaded from Releases, although I would return time column with fractions as well.

from atsd-jdbc.

datetime works ok with the 1.4.9 downloaded from Releases, although I would return time column with fractions as well.

Same, should be working without driver upgrade when correct metadata is returned

from atsd-jdbc.

@rodionos Could you try with latest snapshot on latest ATSD, please?

from atsd-jdbc.

Version number increase required because ATSD may send general number type as metadata. JDBC driver didn't recognized it and used varchar fallback. Since 1.4.10, number is alias for decimal in JDBC driver

from atsd-jdbc.

I don't see this error on the 1.4.9 version, closing.

from atsd-jdbc.