First of all I don't think it will be a real problem.
But if you really matter, you may use sql-query (of course not bound
to your class), or maybe create a bunch of "lightweight" classes that
will contain "just" columns/associations you need in particular case.
Super-massive/super-universal class, that is used "everywhere" in the
application, is not always the best choice...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to