since Hibernate makes this assumption I think it's fine to enforce that. On 15 September 2015 at 17:36, Steve Ebersole <st...@hibernate.org> wrote:
> We have a Pull Request[1] to add a feature to allows Dialects to enforce > that all columns making up a primary key are defined as non-nullable. > Specifically, apparently Teradata will barf if the PK is defined over > columns that are nullable. > > The PR focuses on exporting the table/pk. However, Hibernate overall makes > the assumption that all PK columns are non-nullable. So I wonder if we > ought to just enforce that in the mapping layer. Thoughts? > > [1] https://github.com/hibernate/hibernate-orm/pull/1059 > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
