You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the case of @NamedNativeQuery, it might even be useful to add a way to specify the tables or entities affected by a native query, to allow auto-flush to work correctly:
public @interface NamedNativeQuery {
...
FlushModeTypeflushMode() defaultAUTO;
CacheStoreModecacheStoreMode() defaultUSE;
CacheRetrieveModecacheRetrieveMode() defaultUSE;
inttimeout() default -1;
// control over auto-flushString[] affectedTables() default {};
Class<?>[] affectedEntities() default {};
}
The text was updated successfully, but these errors were encountered:
Currently, a
@NamedQuery
or@NamedNativeQuery
may specify query hints using the verbose and stringly-typed annotation@QueryHint
.I propose making certain "hints" available in a typesafe way, for example:
In the case of
@NamedNativeQuery
, it might even be useful to add a way to specify the tables or entities affected by a native query, to allow auto-flush to work correctly:The text was updated successfully, but these errors were encountered: