When getting JDBC types from the database (e.g. for creating a table based off a query), DataExpress needs to use the metadata to ascertain what the type is. In most cases this is not an issue, but there are rare cases where this can fail. In one example case, SQLite will report a JDBC "Null" type for the column data type. For other databases, stored procedures may make it impossible to determine the type. For these scenarios, rather than total failure, DataExpress should warn that the type is not fully supported. The column on the new table should be created as a VARCHAR and then the data values should be coerced. The question remains what the view size of the VARCHAR should be, bu this likely can come from the database metadata's maximum VARCHAR size.
When getting JDBC types from the database (e.g. for creating a table based off a query), DataExpress needs to use the metadata to ascertain what the type is. In most cases this is not an issue, but there are rare cases where this can fail. In one example case, SQLite will report a JDBC "Null" type for the column data type. For other databases, stored procedures may make it impossible to determine the type. For these scenarios, rather than total failure, DataExpress should warn that the type is not fully supported. The column on the new table should be created as a VARCHAR and then the data values should be coerced. The question remains what the view size of the VARCHAR should be, bu this likely can come from the database metadata's maximum VARCHAR size.