TUniQuery and "Data type is not supported"
Posted: Fri 08 Mar 2013 09:06
If a TUniQuery is used to query a database that has a field type that is not supported, it will throw an exception, mentioning "Data type is not supported".
An example of this are the XML fields in the Customer tables of the DB2 'sample' database.
I've written a browsing type of application and find that when exploring various tables, it is not even able to retrieve a single record when encountering such a field.
Is there some approach I can use to get around this? If not, is this something that can be addressed in the product?
Even if support for XML or any other unsupported field types cannot be handled, how about the simple idea of just creating a dummy field of the same name (maybe a varchar(1), maybe with all the row values as a single question mark) as a placeholder, and at least allow the query to complete? Maybe this should be an option, so as to now affect current functionality. Any solution would be better than the exception and no data.
An example of this are the XML fields in the Customer tables of the DB2 'sample' database.
I've written a browsing type of application and find that when exploring various tables, it is not even able to retrieve a single record when encountering such a field.
Is there some approach I can use to get around this? If not, is this something that can be addressed in the product?
Even if support for XML or any other unsupported field types cannot be handled, how about the simple idea of just creating a dummy field of the same name (maybe a varchar(1), maybe with all the row values as a single question mark) as a placeholder, and at least allow the query to complete? Maybe this should be an option, so as to now affect current functionality. Any solution would be better than the exception and no data.