[
https://issues.jboss.org/browse/TEIID-2827?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-2827:
------------------------------------
I got around the problem by altering the columns to make them nullable, but that
shouldn't have had to be the solution. And its interesting that it only focused on
these 2 columns, when there were other columns that are not nullable and do not provide a
default value.
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