Yeah from your example it's pretty clear the validations could only inspect columns in the record itself, not perform data access. Even a simple and common use case like checking for a duplicate in a unique column doesn't buy you anything and only makes sense on insert.
Anyways, thanks for the quick responses. I'll post to the group when I have something. Thanks, D On Monday, June 10, 2013 9:12:40 AM UTC-4, Lukas Eder wrote: > > Hi David, > > > 2013/6/10 David Fox <[email protected] <javascript:>> > >> Excellent, thank you! I will see how much I can do with generating the >> built in JSR-303 validators. >> >> I didn't want to get ahead of myself, but had also thought about a SQL >> parser for more complex expressions. When I think of how Hibernate does >> things, the validators that one might write for a class are in almost all >> cases impossible to push into the database schema. This is why hbm2ddl only >> utilizes a small number of the annotations in its generation. However, >> coming from the database up to Java gives us a lot more flexibility. > > > That's what it looks like, at first. But what would you do with a CHECK > constraint like this one: > > CHECK (a < ANY (SELECT x FROM b)) > > -- 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/groups/opt_out.
