John > I've always had mixed feelings about this: in some ways using > triggers, stored procedures and the like seem to me like spreading > your application logic in too many places. I can see where they'd be > useful though, too. > No. ALL the business logic should be where it belongs, with the data (Think OOP, where is the logic?) Your application is a "view", a "client". That's it. You should not have any business logic there. Data entry validation, sure, as it makes for a better user interface (still, the database should check for this too)
> Just be sure your app knows how to deal with integrity failures. > Can't. Only the DB knows about transactions, COMMIT and ROLLBACK. > I'd imagine its a little lower on the priority list, mostly due to > the fact that different engines handle things so differently, but > Nate and PhpNut will have to give the definitive answer on this one. > No. DB engines handle things differently INTERNALLY. The interface is the same. Right now, Cake works with PostgreSQL as well as with MySQL (and maybe others). The simple fact is that a MySQL background is not the proper way to get a good SQL background. Bernard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
