Menu
▾
▴
hibernate-issues
|
From: Steve E. (JIRA) <no...@at...> - 2006-03-07 10:50:39
|
query cache and collection fetches
----------------------------------
Key: HHH-1543
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543
Project: Hibernate3
Type: Bug
Components: core
Reporter: Steve Ebersole
Assigned to: Steve Ebersole
Priority: Minor
Whenever query results are served from the query cache, collections are not initialized (regardless of whether join fetching is specified in the query or the metadata).
For example, consider:
from Customer c
join fetch c.orders
When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Peter N. (JIRA) <no...@at...> - 2006-03-07 10:50:42
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543?page=comments#action_22403 ] Peter Nigl commented on HHH-1543: --------------------------------- I'm looking forward to that fix, because that would improve our application a lot. I see your description, nonetheless I wonder that I can acces the data on the server (after doing the query) and when sent to the client they are gone (LazyInitializationException). > query cache and collection fetches > ---------------------------------- > > Key: HHH-1543 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > > > Whenever query results are served from the query cache, collections are not initialized (regardless of whether join fetching is specified in the query or the metadata). > For example, consider: > from Customer c > join fetch c.orders > When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-03-07 21:30:52
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543?page=all ] Steve Ebersole updated HHH-1543: -------------------------------- Fix Version: 3.2.0 3.1.3 > query cache and collection fetches > ---------------------------------- > > Key: HHH-1543 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0, 3.1.3 > > > Whenever query results are served from the query cache, collections are not initialized (regardless of whether join fetching is specified in the query or the metadata). > For example, consider: > from Customer c > join fetch c.orders > When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-03-07 21:30:52
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543?page=comments#action_22412 ] Steve Ebersole commented on HHH-1543: ------------------------------------- I am not able to reproduce this phenomena. The collections are lazy after resolution from the query cache. Thus if you serialize them to the client as-is, they will not be initializable. However, if you initialize them before serializing them, then the client can access them fine after deserialization. At least that is how I took your comment. > query cache and collection fetches > ---------------------------------- > > Key: HHH-1543 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0, 3.1.3 > > > Whenever query results are served from the query cache, collections are not initialized (regardless of whether join fetching is specified in the query or the metadata). > For example, consider: > from Customer c > join fetch c.orders > When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-03-07 21:30:55
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543?page=all ] Steve Ebersole updated HHH-1543: -------------------------------- Description: Whenever query results are served from the query cache, fetched associations are not initialized (regardless of whether join fetching is specified in the query or the metadata). For example, consider: from Customer c join fetch c.orders When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. Same for entity fetches. Same for cached criteria query results was: Whenever query results are served from the query cache, collections are not initialized (regardless of whether join fetching is specified in the query or the metadata). For example, consider: from Customer c join fetch c.orders When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. Summary: query cache and fetches (was: query cache and collection fetches) > query cache and fetches > ----------------------- > > Key: HHH-1543 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0, 3.1.3 > > > Whenever query results are served from the query cache, fetched associations are not initialized (regardless of whether join fetching is specified in the query or the metadata). > For example, consider: > from Customer c > join fetch c.orders > When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. > Same for entity fetches. > Same for cached criteria query results -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-03-16 15:38:16
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543?page=all ] Steve Ebersole updated HHH-1543: -------------------------------- Fix Version: (was: 3.1.3) (was: 3.2.0.alpha2) 3.2.0 > query cache and fetches > ----------------------- > > Key: HHH-1543 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > Whenever query results are served from the query cache, fetched associations are not initialized (regardless of whether join fetching is specified in the query or the metadata). > For example, consider: > from Customer c > join fetch c.orders > When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. > Same for entity fetches. > Same for cached criteria query results -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-03-27 17:36:39
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543?page=all ] Steve Ebersole updated HHH-1543: -------------------------------- Fix Version: (was: 3.2.0 cr1) 3.2.0 > query cache and fetches > ----------------------- > > Key: HHH-1543 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > Whenever query results are served from the query cache, fetched associations are not initialized (regardless of whether join fetching is specified in the query or the metadata). > For example, consider: > from Customer c > join fetch c.orders > When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. > Same for entity fetches. > Same for cached criteria query results -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:50
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543?page=all ] Steve Ebersole updated HHH-1543: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > query cache and fetches > ----------------------- > > Key: HHH-1543 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > Whenever query results are served from the query cache, fetched associations are not initialized (regardless of whether join fetching is specified in the query or the metadata). > For example, consider: > from Customer c > join fetch c.orders > When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. > Same for entity fetches. > Same for cached criteria query results -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-06-28 05:43:00
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543?page=all ] Steve Ebersole closed HHH-1543: ------------------------------- Fix Version: (was: 3.2.0) Resolution: Won't Fix fetching is a hint, not a guarentee > query cache and fetches > ----------------------- > > Key: HHH-1543 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > > > Whenever query results are served from the query cache, fetched associations are not initialized (regardless of whether join fetching is specified in the query or the metadata). > For example, consider: > from Customer c > join fetch c.orders > When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. > Same for entity fetches. > Same for cached criteria query results -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X