-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: Guideline: When not to have a collection property ?
PostPosted: Thu Dec 16, 2010 4:37 am 
Pro
Pro

Joined: Mon Apr 16, 2007 8:10 am
Posts: 246
Hello,

I'm currently coding a Dao layer with quite a few tables / classes.

Some of them have properties that are collections.

My own design guideline regarding when not to have such a property collection, is when the size of the collection is likely to grow big, into the hundreds of items if not thousands.

Is that a sensible guideline ? Or am I being too conservative here ?

My concern is to avoid loading into memory a huge collection of items that would impact the performance of the application.

Thanks for your tips.

Stephane


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.