When i first started working at Surfari.com with maverick
and eduardo, i asked mav this very question.
We were using MySQL at the time, and he explained that the MySQL people were more interested in speed than features.
Conversely, the Postgres people were more interested in
features than speed. Since we didn't need transactions or
inner selects and we did need speed, maverick chose
MySQL.
Flash forward to now. Postgres has managed to finally catch
up with MySQL in the speed department, but MySQL is still
behind Postgres in the feature department. Me?
I still use MySQL simply from habit, but i still haven't
worked on anything serious enough that requires triggers
or transactions. RI, views, and inner selects are good, but
not completely necessary. If you need them or anticipate
needing them (or any of the other features that Postgres
has), use Postgres. As long as you are using Perl, you will
be smiled upon favorably by the Gods. ;)
jeffa
L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
