Internal Website Search

191-200 of 200 resultsRefresh

Annotate a Map field with @ElementCollection or @Basic

; And when it is valid why @Basic is faster at runtime. It could be due to the different default fetch value ... /jpa/Basic">EAGER for Basic). You may try using an @ElementCollection(fetch ... I tested it already with @ElementCollection(fetch=FetchType.EAGER)

Entity with java.util.Date column gives ClassCastException in BIRT

.odaconsumer.ResultSet.fetch( at at at

Accessing objects to make them available after EntityManager close?!

. A more conventional method is to fetch">define the fetch ... _fetch">JOIN FETCH. Alternatively you may consider the non standard

Puzzler: Not getting cascades on read from Spring context

the children objects correctly, but in the application running in Jetty with Spring, fetching is not ... my context.    -dh dhosek Don Hosek Fetching doesn't work ... > It would be better and more efficient, if possible, to arrange fetching of the relevant data before detachment. support Support

Multi threading on DMOs by lazy loading

? Example: class EntityZ { @OneToOne(fetch = FetchType.LAZY) EntityX fieldX; @OneToOne(fetch = FetchType.LAZY) EntityY fieldY; @ElementCollection (fetch = FetchType.LAZY) List<String> list; } We want to load

Cast exception?

> From just fetching a single result: TypedQuery<Player> ... ) So basically the query fetched the persistent fields and built a Player instance ... , but then some testing revealed that there is no error on the fetching request. I could have written

List of Enum Values in an entity

to solve the problem is to change the fetch policy of the field from LAZYfetch=FetchType.EAGER) List<GuestFlag> flags; According to our checks ... this error / warning try: private @Basic(fetch=FetchType.EAGER) List

Changes in detach behaviour?

during em.close()? mosi0815 Ralph Moser The last builds include fixes for some fetch ... setting EAGER fetch explicitly. How is getUserByNamefetching of primitive fields is a bit to much. mosi0815 Ralph Moser

Broken @ManyToOne reference

@ManyToOne(fetch = FetchType.EAGER, cascade=CascadeType.ALL, optional=false) private B b; @Id ... Tsichevski This is an unexpected behavior, B instances should be fetched eagerly in this case. fetch = FetchType.EAGER)   public AbstractParent prn; } the output


{ @OneToOne(fetch = FetchType.EAGER) private CacheableJobInfo ji; @OneToOne(fetch = FetchType ... , but explicitly by calling persist. The problem dissapeared when removing the @OneToOne(fetch