The idea behind using a view is that you can effectively alias your existing tables, but with cake conventional field names etc, so that the cake magic will work automatically with the views.
If that´s not to your liking, you can define primary and foreign keys etc for models that dont use the cake conventions - see the manual for details. Happy baking! On Aug 27, 10:52 pm, Adwin Wijaya <[EMAIL PROTECTED]> wrote: > Yes, I was thinking to use View as well (if the cake doesnt allow me) > but the view will be same 100% with the table (select * from > mytablename), but when i rethink about that, it will confuse other > developer a bit in the future, so i will keep usibng the same > table :) > > On Aug 27, 7:51 pm, wgrant <[EMAIL PROTECTED]> wrote: > > > > > You might consider using views for this. Especially in this case > > where you are going to expose data to your external users, you may > > find that there is data that you want to hide from them. Database > > 'views' will let you create virtual tables, named and organized > > however you want while omitting sensitive fields. You can also apply > > more restrictive privileges to your views.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
