Thanks for your response Troy. Good to know I'm not recording unecessary data.
As to the second question, there are some associations that I will need to remove when a record is deactivated. am i able to access the CakePHP Model associations array via the controller, and should I be doing this at all? Or should it be something written in the Delete function of each controller where this is necessary? thanks guys, freedom On 14/09/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > My application requires that in order for orders to be visible in the > future albums never can really get "deleted", but their status is set > to inactive. Also, anywhere in my code where I execute a findAll I add > Album.active = 1. This way I don't get the inactive ones. > > So, yes there are cases where you wouldn't want the actual DB data > deleted, but instead just inactivated. The best solution I have is to > add that parameter to any necessary queries where you don't want to > know the inactive ones. > > As such I have deactivate function and a delete function for the model. > This way they can deactivate (or it does on it's own after set period > of time) or they can actually delete it. But due to how orders are > built from pictures in albums it is really impractical to delete the > albums and photos altogether or the orders would be left missing > necessary data. > > This requirement is probably few and far between. But it can be a > necessity. Think store and discontinued items. They still know they > had the item in the past, but just don't show it to everyone. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
