Re: [fw-db] views and dependant rowsets

I've read (in this mailing list) that it's OK for views to have read-only access to the database, usually through view helpers. I'm not sure if that's what you mean, but I think it might be related.

As far as a wrapper class, I've done this myself for my "user" class, since there are several tables involved in a user account (multiple e-mail addresses, professions, interests, etc.). They are all accessible through this user class and the user class knows and handles the relationships between the tables. It can also create new users and update users, but I never call those methods from within a view.

I hope this helps. :)

On Mon, Oct 27, 2008 at 7:24 PM, tony stamp <tonystamp@hotmail.co.uk> wrote:

Is it condidered ok for a view to have access to a rowset, to obtain
dependant rowset information? Otherwise, how else can dependant row
information (say information that needs to be composited from several

tables) be passed to the view? Or would it be better to wrap an entity that
has several dependant tables on it into it's own class, that acts as a sort
of manager/director for all communication through it's own and dependant
information?

thanks.
--
View this message in context: http://www.nabble.com/views-and-dependant-rowsets-tp20200829p20200829.html

Sent from the Zend DB mailing list archive at Nabble.com.

--
-Hector