|
Ok. Let's say you have a list container that holds records from your result set. Say a vector of the base object. Now, in this thread I've read that you shouldn't select fields you don't need. I've also heard that to minimize work with table updates, to follow the example as Fred has shown. (BTW, great example). Now, if I am hiding the data from my user, the container they use will need to contain all the fields, since they really won't know which fields (or members) they will need. So, this eliminates the "don't request a field unless you're going to use it" idea, at least in my view. Because the end user doesn't deal with a result set or affect the fields selected and used in the container when it is loaded. They simply .load() the class. I can think of ways that the user could be allowed to choose the fields to load, but then how would the class loader deal with that? thinking out load again...
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.