I could only recommend PostgreSQL in cases where your data is highly sensitive or "mission critical", as it has better transaction and constraint support, but what I have found is that it does not scale nearly as well as MySQL, especially when MySQL clustering is taken into consideration. A company I work with has database servers containing 7TB of voter registration data, and querying is extremely slow. The Postgres query scheduler works in such a way that even fast queries are held up in the queue by longer queries which block other requests from coming through.
I have started to help them restructre their application to offload some of the less sensitive data onto MySQL servers, which have proven to be far more efficient. Postgres is a highly capable database server with a boatload of "enterprisey" features, but those features add significant overhead, making it much less efficient than MySQL. On Mar 10, 12:00 pm, "Pepepaco" <[EMAIL PROTECTED]> wrote: > My personal advice is: Go with PostgreSQL, if your ISP supports it. > PostgreSQL is by far more powerful and feature complete than MySQL, > and scales very well, so probably you won't ever need to change to > other DBMS just because PostgreSQL lacks something. I will say more: > if you get used to PostgreSQL, it's difficult to go back to MySQL; it > looks like a "toy" database in comparison. (Note: this is my personal > opinion, I don't want to start a flame war here.) > > That said, if your application is not very "data intensive", both > databases may serve you well. And by using Cake, you can change easy > between both databases, if you stick to "good practices": keep all > your database stuff into your models, don't embed raw queries in your > code unless there is no other option, and in this case hide the > details into model functions that return "coocked" data. > > Hope this helps... > > On 9 mar, 20:43, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > I'm in the planning stage of what will hopefully become my first non- > > trivial web app. I'm trying to minimize future pain resulting from > > poor planning, and have been reading up on DB trivia. > > > If I use MySQL, how do I choose between MyISAM and InnoDB? What are > > the trade-offs? It seems InnoDB is the way to go if I want to handle > > rollbacks and such, but MyISAM may produce considerably shorter query > > times. Is this true? > > > Should I use PostreSQL instead? I find the popularity of MySQL > > comforting, but the PostreSQL crowd has some convincing zealots. > > > At the end of the day, I'm not doing anything too complicated, and I > > just want to minimize DB-related stress in the long run. > > > Thanks in advance. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
