Wow. I'd stop listening to whomever it is that's telling you these
stories. Really.
The difference between the MyISAM and InnoDB storage engines centers on
InnoDB's excellent support for transactions (MyISAM has none), InnoDB's
row versus full table locking with MyISAM, and general ACID compliance
versus non-ACID compliance. But these features aren't related (as far as
I have ever heard or seen in practice) to basic SQL syntax.
Check out the excellent MySQL documentation on-line that succinctly
explains what MySQL can and cannot do today with each of the storage
engines available to it:
General MySQL Features and Limitations
http://dev.mysql.com/doc/mysql/en/Features.html
MySQL SQL Syntax
http://dev.mysql.com/doc/mysql/en/SQL_Syntax.html
MySQL Table Types, their features and drawbacks
http://dev.mysql.com/doc/mysql/en/Table_types.html
etc.
This is by no means a "RTFM" but an encouragement to quickly find
answers to many of these incorrect concepts others seem to have given
you about MySQL. Read the documentation MySQL provides and you'll know
first hand what the real problems are! :) But you'll also see what's
useful, perhaps, and find something worthwhile.
HTH,
Robert J Taylor
robert@stripped
As an aside:
The freely accessible, transparent On-line documentation MySQL AB
provides for its products is one of the telling traits of the company
and its products as a whole. I personally have rarely seen such candor
about one's own products in publicly accessible documentation. Helpful
and refreshing.
David Blomstrom wrote:
>It says, "Currently, these features are available for
>MyISAM tables only."
>
>Does that mean you can't join MySQL tables that use
>these features? I haven't even learned how to make a
>join yet, but I was told that it can only be done with
>InnoDB tables.
>
>
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Movies - Buy advance tickets for 'Shrek 2'
>http://movies.yahoo.com/showtimes/movie?mid=1808405861
>
>
>
