Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > LLBLGen Pro Runtime Framework> Lazy loading for Blob type entity fields
 

Pages: 1
LLBLGen Pro Runtime Framework
Lazy loading for Blob type entity fields
Page:1/1 

  Print all messages in this thread  
Poster Message
SyN
User



Location:

Joined on:
10-Jan-2006 14:07:38
Posted:
5 posts
# Posted on: 10-Jan-2006 14:30:46.  
Hi,

I am currently evaluating LLBLGen Pro demo using the selfservicing template for Visual Studio 2005 and an Oracle database.

I would like to know if there is a way to delay the fetching of BLOB type entity fields until such a field is actually accessed via the matching (readonly) property of th entity (i.e. I would like to transparently lazy load the BLOB field to avoid hogging memory and bandwith resources just as LLBLGen allows me to do with 1:1 relationships).

Thank you in advance.

Sincerely,
Jean.
  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 10-Jan-2006 14:39:17.  
This is currently not possible, but it's planned for v2 which is scheduled for late Q1 2006

Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
SyN
User



Location:

Joined on:
10-Jan-2006 14:07:38
Posted:
5 posts
# Posted on: 10-Jan-2006 14:41:18.  
Thank you for this quick reply.

I guess I will just unmap the BLOB field from the entity and fetch the BLOB manually with good old SQL then.

Sincerely,
Jean.
  Top
Walaa
Support Team



Location:

Joined on:
21-Aug-2005 16:03:48
Posted:
14584 posts
# Posted on: 10-Jan-2006 14:51:23.  
I faced this need before, so I designed my database in a way to put my BLOB fields in another table having 1:1 relation with the main table so that it would be loaded only on demand.

  Top
RobinT
User



Location:
Netherlands
Joined on:
04-Jun-2007 12:41:20
Posted:
6 posts
# Posted on: 19-Jun-2007 18:00:23.  
I have the exact same problem, but I dont feel like splitting up the table.
Has this been implemented yet? If so, how do I mark a field as "lazy loadable" (could not find it in the manual so far) ?


Thanks
  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 20-Jun-2007 10:56:24.  
RobinT wrote:
I have the exact same problem, but I dont feel like splitting up the table.
Has this been implemented yet? If so, how do I mark a field as "lazy loadable" (could not find it in the manual so far) ?


Thanks

It has been implemented in v2.5, currently in beta. Please look into 'excluding fields' in the beta docs for v2.5.


Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
RobinT
User



Location:
Netherlands
Joined on:
04-Jun-2007 12:41:20
Posted:
6 posts
# Posted on: 20-Jun-2007 15:31:20.  
Ok thanks I found it.

The docs only give an example for adapter though. I had look around for while for selfservicing, as only the very last version on GetMulti() turned out to have an entry for an exclusion list. Maybe add a slight update to the docs?
  Top
Walaa
Support Team



Location:

Joined on:
21-Aug-2005 16:03:48
Posted:
14584 posts
# Posted on: 20-Jun-2007 15:53:47.  
Thanks, will take this into consideration, as the documentation is still in beta too.

  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 20-Jun-2007 20:01:43.  
Yes, the docs are very raw and will be updated soon. I had hoped to have proper docs in development already, as we purchased a license for Madcap Flare, but we ran into a major bug with that immediately, so we're currently a bit stalled in that progress. Hopefully it's fixed very quickly.
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
RobinT
User



Location:
Netherlands
Joined on:
04-Jun-2007 12:41:20
Posted:
6 posts
# Posted on: 21-Jun-2007 11:45:41.  
Another small suggestion for the final release might be to include the exclusion field in an other overloaded version of the GetMultiManyToOne() generated methods/templates. Regular Smiley

  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 21-Jun-2007 12:16:51.  
RobinT wrote:
Another small suggestion for the final release might be to include the exclusion field in an other overloaded version of the GetMultiManyToOne() generated methods/templates. Regular Smiley

These methods are more or less used for lazy loading routines. I've to think about adding an overload for these methods as well, as it will make the generated code bigger, which isn't something I'm really fond of doing.
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
sparq
User



Location:

Joined on:
14-Mar-2010 22:56:10
Posted:
49 posts
# Posted on: 19-Feb-2018 22:27:07.  
Otis wrote:
It has been implemented in v2.5, currently in beta. Please look into 'excluding fields' in the beta docs for v2.5.


I am using 5.3 and this feature doesn't seem to exist. "Excluding fields" does just that, it doesn't lazy load when calling the excluded property getter.

Did this get dropped at some point?


  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 20-Feb-2018 09:30:17.  
Lazy loading excluded fields was never implemented as such, it's always been explicit (so you have to explicitly load the excluded fields. Here's why: https://www.llblgen.com/Documentation/5.3/LLBLGen%20Pro%20RTF/Using%20the%20generated%20code/SelfServicing/gencode_excludedfields.htm#the-excludeincludefieldslist-class (see note at the bottom of that paragraph)

Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.