I'm reading your concerns and your response to perrin as "he doesn't understand its architecture."
Now, you have very valid points with regards to MySQL's suitability for certain tasks. Oracle is still the gold standard for a reason (and it's not its pricepoint!). That said, MySQL is suitable for most tasks, assuming you set certain defaults appropriately. I don't ever do anything unless it's in InnoDB or NDB (if I need clustering). I always use the strictest sql mode and I set all my charsets to Unicode or Latin-1 (depending). There are certain features I will never use and certain features I don't consider optional. Same as my thoughts on Oracle, Sybase, and DB2. Oracle's defaults suck horribly. There isn't a single Oracle DBA that would ever consider using them. Does that make Oracle a bad RDBMS?
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
-
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.
|