• I’m going to get a book on (My)SQL so I can learn a bit more about it. My question is this… I know that MySQL is a specific product/version of SQL. But, how does MySQL differ from SQL? Would I benefit more from getting a book on MySQL since that is what I mostly use (I have the option for postgres on my site, but don’t use it), or would it be better to get a book on SQL that is software independent so I could transfer that knowledge to other versions of SQL?
    Thanks for your input. 🙂

Viewing 4 replies - 1 through 4 (of 4 total)
  • Well, SQL isn’t a product… it’s a language… Now, if you mean the difference between MySQL and MSSQL (Microsoft’s SQL – aka Sql Server) then there are a lot of differences. In general SQL is SQL is SQL, and there is a standard, which most databases stick too, but some also add on other features.
    I would start out working with a book that deals with Standard SQL (or ANSI SQL). 99% of what you would learn there will work just about anywhere else. All SQL databases have their differences, it’s just a matter of learning the nuances which can only really come with time and experimentation.

    Thanks for the response, TG. Actually, I wanted to know the differences between MySQL and standard, non-software specific SQL. As I said above, I know MySQL is a specific product/version (never said SQL was a product *grin*). I was just wondering if I’d cripple myself at all learning MySQL first, since learning software is not necessarily learning the whole language. MySQL only contains a subset of all the capabilities of SQL as I understand it and I don’t want to begin to rely on some ability or function only to find it is specific to the MySQL software and not SQL as a whole.
    I may actually pick up books on both MySQL and SQL since I use MySQL, but would like to have a broader understanding if I ever need to move to MSSQL or postgreSQL, etc.

    Actually, if you can do it in MySQL, it’ll work in just about any SQL. MySQL actualy has more restrictions (like, at the moment inner selects are not supported) than others. So far the biggest difference I’ve run into is the use of the LIMIT keyword. In MySQL, it allows you to determine how many rows to return and starting with what row – something I wish MSSQL had.
    I wouldn’t worrytoo much about crippling yourself by working with MySQL first. It’s just another flavor of standard SQL

    Thanks. That pretty much cinches it for me. 🙂 I’ve ordered this one from amazon:
    Read the first few sample chapters and was impressed. 🙂

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘SQL vs MySQL’ is closed to new replies.