tracker issue : CF-3039726

select a category, or use search below
(searches all categories and all time range)
Title:

Bug 79521:(Watson Migration Closure)Well the main issue is when you have a property marked as lazy in a presistent CFC, when you do a dump of the entity it loads all the lazy tables as well

| View in Tracker

Status/Resolution/Reason: To Fix//

Reporter/Name(from Bugbase): Faisal Abid / Faisal Abid (Faisal Abid)

Created: 08/20/2009

Components: Debugging, CFDump

Versions: 9.0

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 /

Priority/Frequency: Normal / Unknown

Locale/System: English / Platforms All

Vote Count: 3

Problem:

Well the main issue is when you have a property marked as lazy in a presistent CFC, when you do a dump of the entity it loads all the lazy tables as well. This can be quite fustrating to a new commer to ORM and in general anyone wanting to see the data that is loaded and not loaded(lazy). A simple <cfdump loadLazy="boolean" var=#var# /> would be wonderful
Method:

Mark some stuff as lazy and cfdump it :)
Result:

CFDump should not load tables marked for Lazy when using ORM

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3039726

External Customer Info:
External Company:  
External Customer Name: Faisal Abid
External Customer Email: 49A703E141EE933E9920157F
External Test Config: 08/20/2009

Attachments:

Comments:

Instead of a "loadLazyTables" attribute, a "depth" attribute would be preferred so the developer has control over how deep in to the object graph the dump should go.
Vote by External U.
23004 | November 10, 2011 07:02:35 PM GMT
I have a complex object graph and some of the one-to-many loads are huge. I can't use CFDUMP because it litterally loads millions of records out of the db and crashes CF.
Vote by External U.
23005 | November 10, 2011 07:02:36 PM GMT
This bug has been voted..
Vote by External U.
23006 | November 10, 2011 07:02:37 PM GMT