[ https://issues.jboss.org/browse/TEIID-4446?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4446. ----------------------------------- Resolution: Done Updated the code so that we are consistently handling precision/scale. A nominal internal max of max short was introduced as the max precision (half that for scale) when precision is left unspecified - as those are safe for jdbc/odbc/odata metadata (jdbc expects a short scale, and odbc can only properly encode unsigned short). However for backwards compatibility at for now we won't throw an exception if larger values are set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)