Hi all,
First, for some reason, I did not receive latest replies on the mailing
list as emails today. So I just copy and paste Allin's last remark.
Sorry, but I've explored some further issues:
1) "DATUM" is a date string in the format YYYY-MM-DD. This format seems
to cause trouble as an error occurs for the query:
QUERY: "SELECT DATUM FROM OV_AS_LAB_LUMEN.IFO_DATA LIMIT 10"
<output>
SQL query: 'SELECT DATUM FROM OV_AS_LAB_LUMEN.IFO_DATA LIMIT 10'
SQLConnect(dbc,...): SQL_SUCCESS
Number of columns = 1
col 1 (DATUM): data_type invalid, size 10, digits 0, invalid 'nullable'
value!
Number of rows (from SQLRowCount): 10
SQLFreeHandle(SQL_HANDLE_STMT): SQL_SUCCESS
SQLDisconnect: SQL_SUCCESS
SQLFreeHandle(SQL_HANDLE_DBC): SQL_SUCCESS
SQLFreeHandle(SQL_HANDLE_ENV): SQL_SUCCESS
</output>
<ALLIN>
Hold it there! What's the actual SQL data type of this column?
Obviously it's not recognized by gretl (though "invalid" is probably
too strong a judgment). You say it's a "date string", and gretl
recognizes these string types: SQL_CHAR, SQL_VARCHAR, SQL_WCHAR and
SQL_WVARCHAR.
We don't currently handle the SQL_DATE type. That's something I'm
working on right now, but it doesn't sound as if this is an SQL_DATE
column.
</ALLIN>
True, "DATUM" is not of type "date string". According to the DB,
column
"DATUM" is of the type "DATE". I've attached a screenshot of its
details. But I guess that explains the current issue then.
My current workaround is to (1) Fetch "DATUM" as casted ISO8601 date,
and (2) fetch the remaining columns. The resulting data set looks fine then.
Artur