V dokumentacii k Hibernate, kapitola 5.1.13. (one-to-one) sa pise:
|lazy| (optional - defaults to |proxy|): By default, single point
associations are proxied. |lazy="no-proxy"| specifies that the property
should be fetched lazily when the instance variable is first accessed
(requires build-time bytecode instrumentation). |lazy="false"| specifies
that the association will always be eagerly fetched. /Note that if
|constrained="false"|, proxying is impossible and Hibernate will eager
fetch the association!
/Su splnene uvedene podmienky ?
Info wrote:
Zdravim konferenciu,
vcera som kontroloval ake SQL dotazy generuje moja aplikacia pomocou
Hibernate. pouzivam LAZY loading a zarazila ma jedna vec.
ak mam objectA a ten ma OneToOne vztah k objectB , teda v triede ObjectA je
uvedene:
@OneToOne(mappedBy = "objectA", fetch = FetchType.LAZY, cascade =
CascadeType.ALL)
private ObjectB o1;
tak aj napriek tomu ze je tam FetchType.LAZY, potom ako sa vykona SQL select
nad tabulkou pre objectA sa vykonava aj select nad tabulkou pre objectB.
mam aj ObjectC, kde objectA ma s nim vztah OneToMany:
@OneToMany(mappedBy = "objectA", fetch = FetchType.LAZY, cascade =
CascadeType.ALL)
private List<ObjectC> o2;
toto funguje spravne a ziadny SQL dotaz do tabulky objectC nie je.
neviete ako donutit Hibernate aby aj pre vztahy OneToOne pouzival LAZY
loading a nedotahoval zbytocne data.
dakujem
Ivan
________________________________________________
Message sent using Webmail 2.7.9
