You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Brent Daniel (JIRA)" <tu...@ws.apache.org> on 2006/05/25 21:43:30 UTC
[jira] Commented: (TUSCANY-234) column names in config file that
don't correspond to actual table names are silently ignored.
[ http://issues.apache.org/jira/browse/TUSCANY-234?page=comments#action_12413293 ]
Brent Daniel commented on TUSCANY-234:
--------------------------------------
This is a difficult one to address. One of the core design principles of the DAS is to not require configuration for information that can be inferred. Not finding a column in the config would be the normal case, and not an exception. Obviously, this causes some problems in this case where you want to specify config for a column, but it doesn't match the information pulled back from the ResultSet.
Some possible solutions:
1) Implement a "Heavy Validation" mode, where we report warnings on columns in the ResultSetMetadata that don't have an equivalent in the Config, or vice versa.
2) Have some sort of validation tool outside of the runtime that accomplishes the same thing.
3) In this particular case, we may be able to catch exceptions that occur on data retrieval because of a lack of converter. At that point, we could throw an error telling the user to either write a converter or check the config to make sure the converter was specified correctly. This would work in cases where the converter is doing a class conversion, but wouldn't be as useful for other types of converters.
> column names in config file that don't correspond to actual table names are silently ignored.
> ---------------------------------------------------------------------------------------------
>
> Key: TUSCANY-234
> URL: http://issues.apache.org/jira/browse/TUSCANY-234
> Project: Tuscany
> Type: Bug
> Components: Java DAS RDB
> Versions: Java-Mx
> Reporter: Rick Rineholt
> Fix For: Java-Mx
>
> When adding a converter in the config file my case mis matched to the column name this is related to TUSCANY-233 but it seems that if there are no matches altogether there is no check. An exception needs to be thrown that states the table and column that was searched for. Without a fix like this it can real difficult for the end user to isolate this error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org