Hi, We're doing a new project which uses spring-data and we're using Jooq 3.11.1 as our generator only for now.
As part of the generation, there are several tables that are "filtered views" which means they don't have an independent PrimaryKey, but do have the original "id" column which is a unique key in the base table. It does produce a @UniqueConstraint but Spring-data is still not happy with that. Should the use of syntheticPrimaryKeys be adding an @Index annotation as well? As an enhancement request-- it would be great if one column was enough to kick off the annotation since we already have a unique field, just not marked as a primary key. Aram -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
