From: Ivan B. <iv...@cv...> - 2010-08-01 20:15:17
|
Petr Vanek wrote: > it looks interesting. Would it be possible to display NTY (SQLT_NTY) > types too? I don't know status of support for named types (objects, > collections) in OTL and/or Trotl... > > Sure. That is reason why I started working on alternative OCI wrapper library. OTL has support for collection of numbers and varchars. In trotl library I've support for SYS.XMLTYPE and initial support for ANYDATA. Trotl library is easily extensible for other types, but toQValue is not. So I'm looking for some way how to store these types inside toQValue. Now all the DB vendor specific "knowledge" is hidden in connection provider's code and the rest of the application is trying to be universal and DB independent. I hope that these changes will be useful for other databases. I guess that PostgreSQL has even more datatypes that Oracle. Ivan PS: I forgot to mention something in previous email. There are two possible ways distinguish complex types in resultModel and in other higher level classes: - use only virtual methods from the class complexType and not use any dynamic casting. Now I'm using this approach. - register each subclass of complexType using Q_DECLARE_METATYPE. This will assign unique numeric id to each type. This ID can be queried by calling toQValue.Value.userType(). |