Well in that sense, Oracle does cling to some old designs that suck for
most people's use-cases these days; most notably arbitrary-length indexable
text fields. In most Oracle-related applications you are stuck with
either an indexable nvarchar(4096) or an unindexable CLOB field (which
also requires a byte-stream cursor-based access implementation; one
cannot just "SELECT clob_field FROM table" to get a field dump).
The main problem with mysql is that it has historically prioritized speed
and ease of use over data integrity, which a professional DBA
would/should/ought to refuse to compromise over. The DBA and her DBMS is
supposed to be your organization's last line of defense when it comes to
data integrity.
There are far too many cases involving mysql where you end up with
data in, garbage out, and any DBA worth their salt should be cognizant
of that reality.
On 2010-08-18 12:00:15PM -0400, Vick Khera wrote:
> On Thu, Aug 5, 2010 at 10:41 PM, John Gage <jsmgage@numericable.fr> wrote:
> > P. P. S. You want to get to grandma's house. You want to drive a car. You
> > want to learn to drive the car quickly.
>
> You're driving to grandma's house because she needs cataract surgery.
> You don't want to pay the surgeon, you just want to do it yourself.
> But you don't want to read a book. You just want to take the knife and
> dive in.
>
> If you just want to play with toys, then play with toys. If you want
> to get professional results, be a professional or hire one.
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
--
===========================================================
Peter C. Lai | Bard College at Simon's Rock
Systems Administrator | 84 Alford Rd.
Information Technology Svcs. | Gt. Barrington, MA 01230 USA
peter AT simons-rock.edu | (413) 528-7428
===========================================================