Oh just to let you know. Yes I do know what a Unique Index is. We don't really need fanboys to come yell at us that it's 2007. The year doesn't change the fact that doing stuff on the DB engine is safer then in your software. Validation is still very important, but a properly setup database is better.
Instead some intelligent discussion that isn't closed off by mods would be nice. Oh as for the comment that it breaks REST..... You'd just specify both IDs as you should always, using some surrogate key just introduces the chance for bugs, while meaning any database migration in future could be jeopardised. Flame away..... -Ben On Nov 9, 4:31 pm, Mr-Yellow <[EMAIL PROTECTED]> wrote: > YaY!!! > > Nice to know I just spent months designing a massive properly > normalised and indexed database. > Only to findout Cake doesn't support properly designed databases. > > Lock this thread too, just to make sure discussion of their benefit is > quashed and discovery of the feature hole is less obvious. Makes it > easy when this point isn't very well documented and it's so far from > the norm. > > -Ben --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
