Internal Website Search

, but probably due to a massive EAGER fetch that follows the query execution. That eager fetch doesn't happen for example when the query is run the Explorer, and in other cases in ... > fetch you enforce loading of the entire database. support Support Thanks

{ ... @ManyToMany(fetch = FetchType.EAGER, cascade = CascadeType.PERSIST) private List<Conclusion ... { .... @ManyToMany( fetch = FetchType.LAZY, cascade = CascadeType.PERSIST) private List< ... @ManyToMany(fetch = FetchType.EAGER, cascade = {CascadeType.PERSIST, CascadeType.REMOVE

, String> values = new HashMap<>(); @OneToOne (fetch = FetchType.LAZY, cascade ... extends Identifiable { @Index private long stepNumber; @OneToOne (fetch = FetchType ... @ElementCollection (fetch = FetchType.EAGER) private Map<Integer, String> values = new HashMap<

marked as Fetch.LAZY.  I wrote the attached unit test, and then found this: http ... are managed by an open EntityManager, but it is fetched lazily when needed. fetched either. support

String uid; @OneToOne (fetch = FetchType.EAGER, cascade = {CascadeType.REFRESH, CascadeType.DETACH }) private ModelElementImpl element; @OneToMany (fetch = FetchType.EAGER, cascade ... >It might be related to a large eager fetch that affects the performance of further operations.

with @OneToMany(fetch=FetchType.EAGER). Outside the DAO method ... signingDate;     @OneToMany(fetch=FetchType.EAGER, cascade=CascadeType ... ; @OneToMany(fetch=FetchType.EAGER, cascade=CascadeType.ALL)     private ArrayList<

.ALL, fetch= FetchType.EAGER)         private List<Chapter> ... ;         @OneToOne(fetch = FetchType.LAZY, cascade = CascadeType ... @GeneratedValue long id;         @ManyToOne(fetch= FetchType

and fetching Entities afterwards from database. Expected result: Getting changed Entities from ... > and fetching Entities afterwards from database. Expected result: Getting changed Entities from ... elements using UPDATE-Query and fetching Entities afterwards from database. Expected result: Getting

to FetchGroup from JDO. It works like this. First you specify attributes to fetch from ... ); query.setHint(QueryHints.FETCH_GROUP_NAME, "names"); This will be equivalent to query ... .firstName, e.lastName FROM Entity e", Tuple.class); But with fetch group you don't

= "uid") private String uid; @OneToOne (fetch = FetchType.EAGER, cascade = {CascadeType.REFRESH, CascadeType.DETACH }) private ModelElementImpl element; @OneToMany (fetch = FetchType ... MappingImpl { @Id private String uid; @OneToOne (fetch = FetchType.EAGER