Mostly I was thinking that the issue is more of a translation tables that passes what you know about how an existing view returns the data that can enable Cake to map it into what it needs to deal with the data in the Cake types of structure. Since inevitably there will be many 'views' that were not built with cake in mind. My thinking was that one could look at the step between when the data returns from the db before cake begins to apply it's 'special sauce' to the data to see if there might be a way to use a data map that is supplied. More like a plan of attack to offer as a way for cake to become more friendly to existing views. I have used views with cake but always they were not pre-existing ones and so I could really tweek them to return data to cake's liking.
Sam D On 1/29/07, Bernard Grosperrin <[EMAIL PROTECTED]> wrote: > > Samuel DeVore wrote: > > I wonder if some kind of model extension could be proposed by people > > who are deeply involved in the use of views in their database > > environments, one that could create a mapping from what a view returns > > to what it would equate to in cakephp constructed style model queries. > > That could then be used to create the CakePHP style of results > > > That's where my limited knowledge of the classes used by Cake does not > help me: For me, a query on a view return a dataset, just like a query > on a table. They are not different at all, in that regard. > > Bernard > > > > > -- == S. DeVore (the old fart) the advice is free, the lack of crankiness will cost you - its a fine line between a real question and an idiot --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
