:-) Yeah, that's kind of confusing, isn't it? I'm assuming that it should read as follows:
"Hints which can not be processed by a particular database are ignored. Otherwise, invalid hints will result in an ArgumentException being thrown." OpenJPA has defined certain hints (and JPA 2.0 has defined some some hints) that could be used with Queries. Some of these hints do not apply to all databases. So, if you try using one of the hints, for example openjpa.hint.OptimizeResultCount and your designated database doesn't have the capability to provide the necessary processing for this request, then it would be ignored. Otherwise, if you pass in a hint that OpenJPA knows nothing about (let's just say openjpa.hint.FailFast), then you would receive an ArgumentException. The curious thing here is that this seems to contradict the hint processing as defined by JPA 2.0. I believe invalid hints are supposed to be ignored to allow for programming model compatibilities between JPA providers. So, maybe there's some clean up necessary in our documentation. Does this help? We should probably open a JIRA to address this documentation hiccup. If you don't have access to open a JIRA, then let me know and I can open one. Thanks, Kevin On Wed, Dec 2, 2009 at 2:36 PM, KARR, DAVID (ATTCINW) <[email protected]>wrote: > I'm just reading through the docs (1.2.1) right now, and I noticed the > following statement in section 10.1.7, "Query Hints": > > "Invalid hints or hints which can not be processed by a particular > database are ignored. Otherwise, invalid hints will result in an > ArgumentException being thrown." > > I'm a little confused by this. Under what circumstances will a hint be > ignored, and when will it get an ArgumentException? >
