As far as how the objects are mapped, no, you can't do that stuff quite yet. (Well, techincally you could. Set::map takes a class name as an optional second parameter, so you could write a custom model class that adds the methods you wanted, and map the data to it.) But for right now, it just maps the array to a generic object that acts as a dumb data store.
Object-based models are, however, something we plan to do in the future (most likely Cake 2.0). The reasons we chose to stick with an array-based design were that PHP has very strong support for working with arrays, and PHP4 compatibility is a key feature. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
