On Jan 28, 5:46 pm, Bernard Grosperrin <[EMAIL PROTECTED]> wrote: > Chris> I have never used an SQL view and would love to see a real-world > > example of when a view should be used over, say, the CakePHP model > > combined with associations.That's a pretty typical (and kinda sad) answer > > from someone with no real > sql/ database background, and happy with MySQL, which just recently, > (version 5) realised that Views, stored procedures, triggers, etc are > MANDATORY in any serious database engine.( I use Postgresql exclusively > with Cake, and am increasingly frustrated by the numerous limitations of > cake versus a REAL database)
Okay, if you even think about fronting that holier-than-thou PostgreSQL bulls**t, you're going to get yourself banned from this list so fast it'll make your head spin. Having worked extensively with both MySQL and PostgreSQL in production environments, I can tell you objectively that MySQL is more than adequate for *most* applications. The company I work for maintains databases of voter registration records, which is several TB of data, in PostgreSQL. Some queries which would take just a few minutes in a properly-clustered MySQL environment take *hours* on Postgres, which sucks a** by any measurement. That's not to say we don't use Postgres for a reason, but the point is that there's a correct tool for every job, sometimes more than one, but I've had this argument way to many times, and I won't suffer it again here. No more MySQL-bashing or Postgres arrogance. End of discussion. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
