On Fri, 21 Dec 2001, Brian Ashe wrote:
> > The OP won't go wrong with either one, but I suspect she'll find more
> > documentation for MySQL than for PostgreSQL, which might be a
> > significant consideration.
>
> I find this highly inaccurate. The reason being that I believe there is so
> much written to document MySQL is due to the fact that it is not a standards
> compliant SQL implementation and geared towards people looking for some RDBMS
> functionality without having to learn a lot of stuff. Hence the reason for
> some of the "crutches" that MySQL has (that are convenient) that are not in
> other RDBMS to eliviate the need for more advanced programming skills. So
> exclusive docs must be written.
Indeed, this is the reason that I recommend to everyone who asks me which
is best, that they stay away from MySQL. It's not even that the server
doesn't support standard SQL syntax, but they certainly don't promote it
in their documentation.
I think that it's best to start out on a server which supports all the
bells and whistles you don't understand at first so that when you find out
that (and why) you need them, you don't have to restructure all your SQL
code for a new server.
SQL is supposed to promote vendor independence, else it would not be a
"standard". MySQL documents and promotes their own extentions which
frequently are not supported by other servers, even when the standard has
a portable solution. I recommend learning on PostgreSQL, even if you
think you're going to use MySQL.
--
If I had a dollar for every brain that you don't have,
I'd have one dollar. - Squidward to SpongeBob
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
