Re: Comparison, questions for Postgres, MySQL

[Ovid]

Why are you comparing these two? If it's just curiosity, that's fine. If you're looking for a technology solution, have you identified your requirements? One way to approach a situation like that is to list your needs and wants across the top of a page, list the potential technologies down the side of the page and create a grid where you can check off features. Once you have candidates narrowed down, you can start looking at your candidates more in depth, as you are doing now.

Of course, if you've already done that, feel free to disregard this post. I just like to occasionally remind people to find answers to questions, rather than pick the answers and then question them :)

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

[talexb]

Why are you comparing these two? If it's just curiosity, that's fine. If you're looking for a technology solution, have you identified your requirements?

Those are valid questions.

The database is going to be used as a librarian and a recorder of transactions. To me it sounds simple enough that MySQL would do fine, but the CTO wants to be sure that we can do things like views, triggers and rollbacks.

My preference is for MySQL because I know it very well and it has always performed admirably, but if the CTO wants to be able to the fancier things, that's cool. I just wanted to hear about any differences or gotchas that I should worry about.

And if it should happen that we don't use the fancy stuff, I can always go back to MySQL -- Perl lets me do that :) quite painlessly, I understand.

--t. alex
but my friends call me T.