[teiid-issues] [JBoss JIRA] (TEIID-2827) Not sure why Teiid is creating errors based on the database metadata

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12939828#comment-12939828 ] 

Steven Hawkins commented on TEIID-2827:
---------------------------------------

To add a little bit more here, this check is primarily for virtual inserts but has always been in place regardless of the target.  This may seem like somewhat selective of a check given that other things such as referential constraints we leave up to the source system.

Beyond that consideration, what was the full extent of what you saw in the logs?  If we are not at least associating the procedure name with the validation error, then that's an issue.  
                
> Not sure why Teiid is creating errors based on the database metadata
> --------------------------------------------------------------------
>
>                 Key: TEIID-2827
>                 URL: https://issues.jboss.org/browse/TEIID-2827
>             Project: Teiid
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 8.4.1
>            Reporter: Van Halbert
>            Assignee: Steven Hawkins
>         Attachments: createdb.sql, perf-vdb-postgres.xml
>
>
> Using the attached dynamic vdb, against the database that was created using the attached DDL, produces the following errors:
> ERROR: Element Perf.HISTORY."TIME" of history is neither nullable nor has a default value. A value must be specified in the insert.
> ERROR: Element Perf.HISTORY.FILL of history is neither nullable nor has a default value. A value must be specified in the insert.
> Because of these errors, the VDB isn't deployed.
> Not sure why these are not just WARNINGS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira