On Mon, 23 Mar 2020, atecon(a)posteo.de wrote:
I see what you mean (I think!). Getting this right involves some
brain-bending mapping between 1-based SQL columns, 0-based C arrays,
and 1-based dataset series. But I believe this should now work
better in current git.
Allin
Hi Allin,
sorry for another post on this. While the working of SQL_DATE works nicely, I still get
wrongly fetched data if the first selected column is of type SQL_DATE, the second is of
type SQL_VARCHAR -- the format of the remaining ones does not matter.
QUERY 1: WORKS
col 1 (DATUM): data_type SQL_DATE, size 10, digits 0, nullable 2 (?)
col 2 (KLIMA): data_type SQL_DECIMAL, size 4, digits 1, nullable 2 (?)
binding col 2 to xt[0]
col 3 (SEKTOR): data_type SQL_VARCHAR, size 20, digits 0, nullable 2 (?)
binding col 3 to strvals[1] (len = 20)
<>
nulldata NOBS -p
setobs 7 2018-01-01 --time-series
string Q = "SELECT DATUM, KLIMA, SEKTOR FROM ABC.DEF"
data klima sektor obs-format="%s" query=Q --odbc --verbose
print dataset -o
</>
index klima sektor
2018-01-01 1 104.8 gesamt
2018-01-02 2 104.8 gesamt
2018-01-03 3 104.8 gesamt
2018-01-04 4 104.8 gesamt
2018-01-05 5 104.8 gesamt
QUERY 2: FAILS
<>
nulldata NOBS -p
setobs 7 2018-01-01 --time-series
string Q = "SELECT DATUM, SEKTOR, KLIMA FROM ABC.DEF"
data sektor klima obs-format="%s" query=Q --odbc
print dataset -o
</>
As you can see, "sektor" has no string-values any more and for "klima"
are values are missing.
index sektor klima
2018-01-01 1 1
2018-01-02 2 1
2018-01-03 3 1
2018-01-04 4 1
2018-01-05 5 1
Thank you,
Artur