Re: McKoi and Inetsoft Style Reports Problem

NULL columns are only seen for some of the internal tables and meta data 
ResultSet objects, and for some views that define a column as NULL. 
Otherwise, the correct column type is returned for regular user tables. 
  The JDBC driver should work as expected if the product is used to 
browse regular user created tables.  If the browser inspects meta data 
result sets, internal tables (those in the SYS_INFO and SYS_JDBC 
schema), or views, then the reason given by support makes sense if NULL 
columns is an issue for the software.

Note that Mckoi does not return the NULL column type arbitrarily.  It 
only returns it when the column type is either defined as NULL or when 
it isn't known (in the case of some meta-data calls).  It returns the 
correct type in all other situations.

Toby.

Rich Davis wrote:

> Hello,
> 
> I have been trialing a product by inetsoft called Style Reports. (  
> http://www.inetsoft.com/inetsoft/products/prodoverview.html  )
> 
> I have run into a problem when trying to use this product with McKoi.
> 
> Basically, they have an SQL wizard / builder but it cannot cannot 
> retrieve the DB fields from McKoi.  For example, in the screen shot 
> below you will notice that the "msg" table does not show the fields of 
> the table and the subsequent build functions are blank (Fields, 
> conditions, sort grouping)
> 
> <I couldn't send the screen shot; too big>
> 
> A different feature of the builder (the "physical model"  view) the 
> product can show the fields.  When I opened a case with their support 
> they pointed me to this issue on the McKoi list:
> 
> http://mckoi.com/database/mail/subject.jsp?id=5898&highlight=column+null+type+#MSG_5898 
> 
> 
> And here was his explaination when I explained that McKoi works in one 
> portion of their product wizard and not in another:
> 
> It is hard for me to speculate the exact reason for this, as I have to
> factor in the database driver too. The reason I think this happens is
> because for physical models we do not consider column types, whereas while
> building queries we do, and since the database driver is known to return
> null for column types this is a probable cause.
> Please refer to the link for more information.
> 
> 
> Do you think their explaination makes sense?  Do you think McKoi is the 
> cause and if so do you think it is fixable?  The existing list document 
> indicates that McKoi works to the specification but that does seem to be 
> problematic in this case if it is the cause.  Any help would be greatly 
> appreciated.
> Thanks,
> 
> Rich Davis
> 
> 
> 
> 
> ---------------------------------------------------------------
> Mckoi SQL Database mailing list  http://www.mckoi.com/database/
> To unsubscribe, send a message to [email protected]
> 
> 



---------------------------------------------------------------
Mckoi SQL Database mailing list  http://www.mckoi.com/database/
To unsubscribe, send a message to [email protected]