Slashdot Mirror


MySQL Pocket Reference

Michael J. Ross writes "MySQL database administrators and developers have several options for MySQL reference sources, though naturally none of them are ideal in all situations. The online MySQL documentation is extensive, but the most commonly needed nuggets are buried in its necessarily exhaustive contents. Third-party MySQL reference books can winnow out some of the rarely-used minutia, but they still encompass hundreds of pages, reflecting the complexity of the subject. For quickly looking up the most frequently used command syntax and other details, a MySQL user would usually be best served by a much more compact book, such as MySQL Pocket Reference." Read below for the rest of Michael's review. MySQL Pocket Reference author George Reese pages 96 publisher O'Reilly rating 9 reviewer Michael J. Ross ISBN 059600446X summary Great for quickly looking up the most frequently used command syntax and other details of MySQL

Written by George Reese, this book was published by O'Reilly Media, in February 2003. It may span only 96 pages, and weigh only 3.2 ounces, but it packs a substantial amount of useful information into a diminutive form. The book's material is organized into several sections, covering MySQL installation, command-line tools, data types, SQL, operators, functions, and table types.

After presenting a quick introduction and some other housekeeping topics, the author briefly explains how to install, configure, and start up MySQL, as well as how to set the root password. This RDBMS includes a dozen command-line tools, and the author next provides the briefest of summaries for each one, and more details on the most commonly used one, mysql.

The next four sections compose the meat of the book, as they cover the MySQL data types, SQL query language, operators, and functions. Of all the aspects of any programming language or RDBMS, the one that frequently causes the most confusion — and for which a handy reference guide would be most appreciated — is the proper use of data types. In MySQL Pocket Reference, the author presents all of the MySQL data types, grouped into numerics, strings, dates, and complex types. For each data type, the author shows the declaration syntax, the storage space required, and the purpose of the data type.

MySQL version 4.0 supports ANSI SQL 92, as well as some proprietary extensions, which is true for most if not all substantial RDBMSs. Reese explains the case sensitivity of MySQL for various contexts; the use of literals, including escape sequences; the rules concerning identifier naming and aliasing; and how to insert comments in your code. Much more space is devoted to all of the MySQL commands, ranging from ALTER TABLE to USE. For each command, the reader is shown the syntax, including optional keywords, clauses, and other elements, as well as a generous number of illustrative examples.

The last three sections of the book cover operators (arithmetic, comparison, and logical), functions (aggregate and otherwise), and table types. The section on functions will likely get a lot of use from the average reader, as it is relatively easy to forget the name and parameter list of any function — particularly if it has not been used by the developer for some time, and is not present in the surrounding code.

Like any pocket reference book, this one is not intended to serve as a full reference source or as a MySQL tutorial — of which O'Reilly offers several. Rather, it is best used for quickly answering questions concerning command syntax, operator precedence, function parameter order, or any of the other MySQL language details that are not listed automatically by programming editors, nor otherwise immediately obvious. Yet despite its small size, this book contains information that may be unknown to even some of the most experienced MySQL administrators and programmers. For instance, I had no idea that 2007-04-00 is considered a valid date. (I only wish that my taxes were due on that day.)

O'Reilly Media has a Web page on their site that provides some additional resources related to this book. These include links for reading the reviews offered by other readers, submitting your own review, and checking the errata for the book, of which there are 20, as of this writing — 19 of which have been confirmed.

There appear to be only two flaws in this book. It lacks a list of MySQL reserved words, which is odd for a reference book. Also, the text on every page is set too close to the binding, thus compelling the reader to force open the book more than should be necessary, just to comfortably read the inmost ends of the lines of text. This could be easily fixed in a subsequent edition, by moving the text outwards approximately half a centimeter, since the outer margins are much wider than necessary.

Speaking of editions, because this first edition of the book appeared in early 2003, it covers up to version 4.0 of MySQL. One can only hope that a second edition will be made available at some point in the future, so that it can be brought up to date with all of the new additions to MySQL 5, which are substantial. These include cursors, stored procedures, triggers, and views.

Nonetheless, this first edition would be of value to anyone using MySQL. In essence, MySQL Pocket Reference is neatly organized, extremely portable, and packs much valuable information into a succinct format.

Michael J. Ross is a Web programmer, freelance writer, and the editor of PristinePlanet.com's free newsletter. He can be reached at www.ross.ws, hosted by SiteGround."

You can purchase MySQL Pocket Reference from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

72 comments

  1. Nope. by tomhudson · · Score: 4, Informative

    For quickly looking up the most frequently used command syntax and other details, a MySQL user would usually be best served by a much more compact book

    For quickly looking up the most frequently used command syntax and other details, a MySQL user would usually be best served by a quick trip to google.

    1. Re:Nope. by beckerist · · Score: 4, Insightful

      Unless you work for a company that doesn't allow external web-browsing during hours... In which case I recommend ANYTHING by O'Reilly.

    2. Re:Nope. by Itninja · · Score: 2, Funny

      Totally. How could this book be any 'quicker' that a Google search. Maybe the book using indexing like
      "What's that one query command I used that one time?...... page 156"

      --
      I judt got a nre Kinesis keybiartf so please excusr ant egregiou typos.
    3. Re:Nope. by Anonymous Coward · · Score: 0

      What about when you're coding without Internet access? O'Reilly's Python Pocket Reference has served me well on many a long flight. It's also light reading for the cafeteria when I'm at work.

    4. Re:Nope. by tomhudson · · Score: 1

      Unless you work for a company that doesn't allow external web-browsing during hours... In which case I recommend ANYTHING by O'Reilly.

      Not this - it only goes up to MySQL 4.0. Is *anyone* still using that? Even 4.1 was a big improvement. "on duplicate key update" is a huge time-saver, both in coding and in run-time, when you have a large insert query with many potential dupes. 4.0? Sorry, "on duplicate key" isn't available.

    5. Re:Nope. by tomhudson · · Score: 1

      I guess you could email each section of the book to your gmail account, one section or topic per email, and have google search it for you ... :-)

      I like O'Reilly books - I've got a bunch of them on my shelf - but a pocket reference that only goes up to 4.0 is worse than useless, considering the big changes in 4.1, and especially in 5x.

    6. Re:Nope. by CastrTroy · · Score: 1

      How does anybody work in an environment such as this? I find tons of shortcuts for things I do at work on the internet. Stuff that would never be written down in any textbook. How does working without internet access affect your productivity?

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    7. Re:Nope. by Anonymous Coward · · Score: 0

      It affects it negatively. More appropriately you should ask: how does working WITH internet access DECREASE productivity? As a matter of fact, I'd appreciate it if you could email my boss... I'm sneaky though. Virtual image meant for external VPN, remote desktop to my home computer running OpenVPN, Slashdot from there!

      --beckerist

    8. Re:Nope. by tomhudson · · Score: 2, Interesting

      What about when you're coding without Internet access?

      We all go home.

      My dead-tree reference library is at home. I have the same computer setup at home as at the office (dual-screen linux box). I have a fast net connection. If the internet is off at the office, its because there's either a power failure (in which case the computers aren't working anyway) or the net is screwed up.

      The web guys can't update the forums or the company blogs or the web site, the customer support people can't take their email any more ... in fact, its only the coders who don't really have to go home, since we have our own local servers to test against ... but since I carry my latest backups in my pocket, if I can't get it fixed in an hour or so, I go work from home for the rest of the day, same as a "snow day."

      In fact, I'm kind of wondering why I don't telecommute 3 days a week ... which is something we'll be discussing in the future ...

    9. Re:Nope. by IntergalacticWalrus · · Score: 2, Insightful

      Unless you work for a company that doesn't allow external web-browsing during hours...

      I can't imagine myself working in an environment where I can't access online resources while I'm working. The productivity gain is very significant. Any company that doesn't realize this is clearly managed by idiots.

    10. Re:Nope. by Anonymous Coward · · Score: 1, Funny

      Learn how to use a real database. MySQL losers...

    11. Re:Nope. by 228e2 · · Score: 1

      someone should mod this funny. :p

      --
      Since when does being a Socialist mean 'someone who has a different opinion than me'?
    12. Re:Nope. by Dragonslicer · · Score: 1

      According to their docs, 4.1 is officially End of Life, so you'd hope the answer to your question is no. Unfortunately, I worked on a project about a year ago that was required to run on 3.23.

    13. Re:Nope. by RedElf · · Score: 1

      Hey now be nice some toys need instruction manuals to operate. MySQL just happens to fit in that category.

      --
      You know, I have one simple request. And that is to have sharks with frickin' laser beams attached to their heads!
    14. Re:Nope. by WrongDecision · · Score: 1

      Geeeze dude. I really feel sorry for you. Get another job real quick man.

    15. Re:Nope. by isorox · · Score: 1

      Not this - it only goes up to MySQL 4.0. Is *anyone* still using that?

      We still use 3.23 for broadcast data, because it works, and always has done. It has a ~2 year uptime since the last safety test, and it's a fairly light database (500,000 queries per day).

      New development projects go on to 5.1 and use it's features where appropiate

      One database we have, from an external company, has just moved to 4.1 under pressure from us, although the code that accesses it hasn't been changed. The change was to allow eaier migration path to the next version of their software, and a few nice things like subqueries, this is a more meaty database (220MB of data, 350MB of indexes, 20 million queries per day).

  2. Resume by Slashdot+Parent · · Score: 5, Insightful

    Unless you work for a company that doesn't allow external web-browsing during hours... In which case I recommend ANYTHING by O'Reilly.
    That may be your recommendation. My recommendation would be to polish up your resume.

    --
    They don't grade fathers, but if your daughter's a stripper, you fucked up. --Chris Rock
    1. Re:Resume by FMota91 · · Score: 0

      With MySQL?

      *confused*

      --
      09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C1 bottles of beer on the wall. Take one down, pass it round... Oh, umm...
    2. Re:Resume by EugeneK · · Score: 1

      SELECT * FROM jobs WHERE intertubes='allowed';

  3. Here's my pocket reference... by jmagar.com · · Score: 1
    MySQL Web Page

    Seriously, have you ever found yourself away from an Internet connection lately? I actually have a couple pocket references from years ago, but once the PHP manual and its user submitted comments hit the web, all manuals have adopted this technique, and we are all better off. Pocket references are soooooo 2002.

    1. Re:Here's my pocket reference... by CastrTroy · · Score: 1

      PHP's user annotated reference manual is probably the best thing since the invention of the computer manual itself. How many times have you read the documentation only to still be completely lost as to how something actually works. Having real users put in comments means that after the first person figures out some neat trick, the rest of us don't have to.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    2. Re:Here's my pocket reference... by painQuin · · Score: 1

      Seriously, have you ever found yourself away from an Internet connection lately?
      Yes. I have this pesky social life thing. However...

      Seriously, have you ever found yourself away from an Internet connection while writing SQL queries lately?
      No, I work at a company that understands that to write internet based applications you generally need access to the internet. And I am grateful.
      --
      A guilty conscience means at least you've got one.
    3. Re:Here's my pocket reference... by EvanED · · Score: 1

      Seriously, have you ever found yourself away from an Internet connection lately?

      Yes, during 22 hours of transit, then 3 1/2 hours of transit, then 3 1/2 hours of transit, then 4 hours of transit, then 9 hours of transit. And that's just in the last 8 days.

      (Okay, so during at least a fair portion of that time I could have accessed, for instance, airport Wi-Fi. But a good part of that, without a cell phone with internet access, I would have got nothing.)

    4. Re:Here's my pocket reference... by jmagar.com · · Score: 1
      Nice battery you got there! Mine lasts about 2 hours...

      Your point is valid.

    5. Re:Here's my pocket reference... by EvanED · · Score: 1

      During the 3 1/2 and 4 hour things, that was in the car (I wasn't driving), and I had a power inverter I could have plugged into the cigarette lighter. The longer trips had layovers in places with power outlets.

      Now, I wasn't actually using my computer most of that time (in particular, during large portions of these I was trying to sleep), but I did some of it, and I was coding, and there were times when I wished that I had internet access or had installed the MSDN library.

    6. Re:Here's my pocket reference... by Anonymous Coward · · Score: 0

      It has been a while, but I used to teach technical training courses, and the computers were often setup in a conference room without internet access. I also used Eudora because I had a copy of all my email on my laptop, for reference without internet access. Not Fun, but that's the way it was.

    7. Re:Here's my pocket reference... by Anonymous Coward · · Score: 0

      For those who like "pocket" references in addition to online ones (maybe you don't do well managing more than a dozen tabs at a time ;-), Visibone has been a good resource for me webwise. Here's a sample page of their 4-page MySQL reference: http://www.visibone.com/sql/page3_850.jpg

      No, it doesn't have explanations. But most is self-explanatory those of us using MySQL, and this is highly useful for those of us with tons of data in recognition memory, but not available as perfect recall.

      No, I don't work for them. But I've received excellent customer service, so I figure they deserve a mention here.

    8. Re:Here's my pocket reference... by Zontar+The+Mindless · · Score: 1

      PHP's user annotated reference manual is probably the best thing since the invention of the computer manual itself. ...


      You can post comments to the MySQL Manual(s) as well.
      --
      Il n'y a pas de Planet B.
    9. Re:Here's my pocket reference... by infolation · · Score: 1
      I actually mis-read

      but the most commonly needed nuggets are buried in its necessarily exhaustive contents as

      but the most commonly needed nuggets are buried in its necessarily exhaustive comments because it's the comments section of the MySQL online manual where the real explanations of functions can be found.

      It's a shame somebody can't gather together the most essential comments and publish those in a book.
  4. seriously by Anonymous Coward · · Score: 0

    my dick is a pocket reference

  5. MySQL pocket reference by Bluesman · · Score: 2, Funny

    1) Buy business card stock
    2) Print out cards that say "http://www.postgresql.org"
    3) ...
    4) Profit!

    --
    If moderation could change anything, it would be illegal.
    1. Re:MySQL pocket reference by Anonymous Coward · · Score: 0

      Oh good, someone finally started the inevitable flamewar. I was getting worried at the lack of posts bashing MySQL in favor of Postgres.

    2. Re:MySQL pocket reference by CastrTroy · · Score: 1

      I would love to switch over to Postresql, but my hosting service doesn't support it. Also, my PHP code is littered with functions starting with mysqli_. Is there a good PHP database abstraction layer? Why are we still at a point when we're writing code against a particular database? I shouldn't have to write my own DB abstraction layer either.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    3. Re:MySQL pocket reference by irc.goatse.cx+troll · · Score: 4, Interesting

      or better yet, get a usb thumbdrive and stick SQLite on it so you can ship your product without relying on them having a DBA to set it up on the other side. I still don't see why so many people use MySQL or PGSQL for simple webapps like blogs and CMS systems. You arn't going to have multiple accesses from seperate machines, simultaneous updates, or any other possibly reason for justifying a remote DB. The only reason MySQL is so popular is it was shipped default in so many distros. Switching to PGSQL is just using a different brand of the wrong tool (90% of the time, of course)

      How long does it take you to move your webapp+db to a clean machine? I can just rsync.

      --
      Pain lasts, kid. Its how you know you're alive. Sometimes I think this growing up thing is just pain management-TheMaxx
    4. Re:MySQL pocket reference by IntergalacticWalrus · · Score: 2, Insightful

      Why are we still at a point when we're writing code against a particular database?

      Because all databases are their quirks and various different ways of doing a bunch of little things. Writing fully DB-agnostic code is an utopia. Just like there's no "perfect" framework out there to write cross-platform desktop applications that look and feel right on any given platform.

    5. Re:MySQL pocket reference by CastrTroy · · Score: 1

      Maybe the SQL itself isn't going to be database agnostic, but you should be able to run the query and get a result set back without having to call a function specific to the database. .Net has a pretty good abstraction layer, such that I don't have to worry about which database I'm connecting to, and I can connect to Access, SQL Server, Oracle, MySQL, Excel files, and others without calling functions specific to the database. There will always be little quirks, but I shouldn't have to call different functions to execute a simple select query on different database engines.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    6. Re:MySQL pocket reference by Rakishi · · Score: 1

      How long does it take you to move your webapp+db to a clean machine? I can just rsync. How often do you move your small web blog across machines? I can technically rsync a MySQL database (MyISAM at least) as well and it will work fine on the other end.

      You arn't going to have multiple accesses from seperate machines, simultaneous updates, or any other possibly reason for justifying a remote DB. Unless slashdot links you for example.
    7. Re:MySQL pocket reference by tomhudson · · Score: 2, Funny

      Use the c preprocessor to create your php files. 1. Create a source file "something.php.c" #define DB_SERVER example.com #define DB_USR example_user #define DB_PW example_password #define DB_CONNECT $link = mysql_connect("DB_SERVER", "DB_USR", "DB_PW") DB_CONNECT; 2. g++ -o something.php something.php.tmp 3. grep -v "#" something.php.tmp > something.php This is just an example to get you started, but now you can include all sorts of files at coding time, instead of at run time. So put the #define DB_CONNECT in a separate mysql header, and an equivalent DB_CONNECT in a postgresql header, and #include the one you want. The lack of a preprocessor for most languages is a big problem - this gets around it. You could write a perl/python script t automate the process, and strip out multiple blank lines as well (replacing them with a single blank line for readability).

    8. Re:MySQL pocket reference by xannik · · Score: 1

      Check out the PEAR project's solution. http://pear.php.net/package/MDB2. The code at PEAR is normally high caliber and will make your own PHP code much more robust.

      --

      Go Illini!!!
    9. Re:MySQL pocket reference by Anonymous Coward · · Score: 0

      If you actually think that's a good solution to the problem, kindly never distribute or sell any software you write.

    10. Re:MySQL pocket reference by larry+bagina · · Score: 1

      Is there a good PHP database abstraction layer?

      As of PHP 5, I use PDO (a standard PHP 5 feature). Prior to that, I used Pear::DB which is often available on shared hosting services.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    11. Re:MySQL pocket reference by Doug+Neal · · Score: 2, Interesting

      Take a look at this - http://sqlrelay.sourceforge.net/

      It claims to be able to proxy and load balance database connections, supports different database backends and implements the PHP APIs for MySQL and PostgreSQL itself, so you can use it as a drop in replacement. In theory it should be possible to use it to talk to PostgreSQL using the MySQL API. I was planning to check it out with a view to moving some MySQL/PHP sites over to Postgres, but never did (and don't work at that place any more), so I can't vouch for how well it achieves this.

    12. Re:MySQL pocket reference by Tychon · · Score: 1

      Maybe I'm just oblivious, but isn't that what PDO is included for?

    13. Re:MySQL pocket reference by Shados · · Score: 2, Informative

      Using database abstraction layers and object relational mappers like Hibernate or LLBLGenPro allows for the most part to be DB-agnostic except for the most ressource intensive queries where you need to use DB-specific optimisation, which is rather rare except with reports and such, and even then, 90% of the queries that hit the server pretty hard would be better done on an OLAP system of some kind, so the above are pretty darn good.

      Then again, these tools have disadvantages of their own, but still.

    14. Re:MySQL pocket reference by Shados · · Score: 1

      So true. The ONLY thing that irked me so far about .NET's layer is the method that allows you to figure out the parameters of a stored procedure. Its in OleDb_, Sql_, and Oracle_ providers, but not in Db_, so you either have to use a provider specific method, or have fun with Reflection. It should be implemented at the abstract class level, with maybe a property "SupportDeriveParams" or some such or throw an exception if its not implemented, I don't know. But having to use SqlCommandBuilder.DeriveParameters (or the other provider's equivalents) is the only time I have to touch the DB specific classes, and it annoyes me to no end.

    15. Re:MySQL pocket reference by tomhudson · · Score: 1

      Don't knock it if you haven't tried it. The lack of a decent preprocessor shows in a lot of languages.

      Using the c preprocessor to emit code in other languages is not that far-fetched. Conditional code emission (based on conditional #ifdefs) is darned handy.

    16. Re:MySQL pocket reference by CastrTroy · · Score: 1

      That seems to be what I'm looking for, but why haven't I found it before? Nowhere in any tutorials do I see mention of this. Why do things like mysql_ even exist in the first place? The more I use PHP, the more I start to Love .Net, and Java with their wonderfully organized APIs. The again, most PHP tutorials I've found don't even use prepared queries, leaving open tons of sql injection attacks, so I don't find it completely surprising that most people recommend using a Database API that's tied to the database.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
  6. Winnow? by blantonl · · Score: 1

    winnow [win-oh]
    -verb (used with object)
    1. to free (grain) from the lighter particles of chaff, dirt, etc., esp. by throwing it into the air and allowing the wind or a forced current of air to blow away impurities.
    2. to drive or blow (chaff, dirt, etc.) away by fanning.
    3. to blow upon; fan.
    4. to subject to some process of separating or distinguishing; analyze critically; sift: to winnow a mass of statements.
    5. to separate or distinguish (valuable from worthless parts) (sometimes fol. by out): to winnow falsehood from truth.
    6. to pursue (a course) with flapping wings in flying.
    7. to fan or stir (the air) as with the wings in flying.
    -verb (used without object)
    8. to free grain from chaff by wind or driven air.
    9. to fly with flapping wings; flutter.
    -noun
    10. a device or contrivance used for winnowing.
    11. an act of winnowing.

    --
    Lindsay Blanton
    RadioReference.com
  7. hey mister.. by Anonymous Coward · · Score: 0

    you forgot google, how could you?!?!

  8. BROKEBACK COWBOY NEAL by Anonymous Coward · · Score: 0

    I know of a nice men's room at a rest stop on the Interstate. That's where I go when I'm lonely. You can meet other lonely guys there and comfort one another.

    You can also have similar experiences by attending any Linux installfest.

  9. slownewsday by Anonymous Coward · · Score: 0

    Many real programmers use a) mssql b) oracle or c) postgres

  10. Notes from the Author by smack.addict · · Score: 5, Informative

    #1 I was actually kinda shocked to see a /. review on this, as the book came out in 2003.

    #2 Good news is, I finished up the next edition over the weekend and it should be out (I think) in the early summer. This new edition covers through MySQL 5.1.

    #3 If you don't use stored procs or triggers, for the most part, the things you would need in a pocket reference are still all in the old edition and quite valid. Yeah, I also added more useful information on replication and updated all the SQL syntax, but that is stuff 90% of the population does not necessarily need.

    1. Re:Notes from the Author by Anonymous Coward · · Score: 0

      > Yeah, I also added more useful information on replication and updated all the SQL syntax, but that is stuff 90% of the population does not necessarily need.

      ah, the old mysql ab line - 90% of the programmers don't need:
          - transactions
          - views
          - subselects
          - ansi compliant sql
          - stored procedures
          - triggers
          - referential integrity
          - partitioning
          - online backups
          - non-silent exceptions from errors
          - etc, etc, etc

      essentially, all the stuff that's required on 90% of the enterprise projects these days

    2. Re:Notes from the Author by smack.addict · · Score: 1

      No, that's not what I was saying there. I was saying the syntax guide is still pretty much what it was for MySQL 4.0.

      Now that you say that, however, I would strongly recommend avoiding stored procedures and triggers in any DBMS. They are proprietary and they do nothing that is not better handled in the application logic.

    3. Re:Notes from the Author by ByeLaw · · Score: 1

      Now that you say that, however, I would strongly recommend avoiding stored procedures and triggers in any DBMS. They are proprietary and they do nothing that is not better handled in the application logic.

      Wow, never thought a database expert would say this! Paramatized stored procedures surely perform much better and more securly than injected SQL, plus leaving SQL to be optimized by your DBA and not your application programmer leaves the performance of your database in the right hands?

    4. Re:Notes from the Author by smack.addict · · Score: 1

      [i]Wow, never thought a database expert would say this! Paramatized stored procedures surely perform much better and more securly than injected SQL, plus leaving SQL to be optimized by your DBA and not your application programmer leaves the performance of your database in the right hands?[/i]

      There are ways to accomplish all of this without embedding your application logic in the database.

      First off, using prepared statements instead of plain SQL will take care of the security issues related to SQL injection and performance concerns associated with repeated use of the same statements.

      Second of all, with good web application design, you can wall off your SQL access into modules that can be managed by the DBA without undue expertise in the underlying programming language. I am not at all a fan of automated persistence systems that make it hard for you to touch the SQL access code. I have a home grown, open source persistence system at http://www.dasein.org/ that will do automated persistence but then also allow for performance tweaking.

      Finally, let's not forget we are talking about MySQL and that one of the key strengths of MySQL is that it does not require a DBA. If you have the resources for a full-time DBA, chances are PostgreSQL or Oracle make more sense.

  11. Yes, but does it include... by FuryG3 · · Score: 2, Funny

    The correct spelling of the word:

    Privilig..errr

    Privelig..errr

    Privileges!

    Preferably on the cover of the book.

    1. Re:Yes, but does it include... by a9db0 · · Score: 1

      Oh, to have mod points!

      +2 Funny

      --
      -- "Never underestimate the power of human stupidity." - R.A.H.
  12. MySQL pocket reference..? by suv4x4 · · Score: 2, Interesting

    How on earth, in year 2007, is a book the quickest reference to anything. MySQL provides both instant manual lookup online, and indexed searchable CHM help manual reference.

    1. Re:MySQL pocket reference..? by kpharmer · · Score: 1, Insightful

      > How on earth, in year 2007, is a book the quickest reference to anything. MySQL provides both instant manual
      > lookup online, and indexed searchable CHM help manual reference.

      1. it is small enough to be always handy (keep it in your laptop bag, next to your puter, etc)

      2. since all it has are concise explanations - you'll spend less time wallowing in stuff you don't care about (when you want is something concise)

      3. it is formatted specifically for quick syntax & example checks, rather than for general purpose documentation

      4. there are benefits to books - you can easily add comments to them, you more (sometimes) more easily scan for information, etc, etc.

      I generally avoid mysql, but if I had to use it a lot I might consider this book. Or especially if I had to hit the road supporting some product that used four different databases, mysql just being one. In that case one of these for each database might be useful. But this is the older version (2003), and the author said that you'll want to wait for the new one due this summer to get all the standard stuff that was missing in 2003 (view, stored procedures, triggers, ansi-compatible sql, whatever).

    2. Re:MySQL pocket reference..? by suv4x4 · · Score: 1

      I guess we have some people from the last century visiting us...

      -----------
      1. it is small enough to be always handy (keep it in your laptop bag, next to your puter, etc)

      I have to agree. I saw some experimental graphical interfaces on TV yesterday, and it looks really promising, Not only you get to work visually, but you get to lay out your screen space as you want (for example, place shortcuts to needed references on your "task bar" they call it). And the best thing is: you can run multiple apps at once! But.. with my DOS, it's too much hassle to exit my text editor and open some shitty computer book reference all the time.

      Of course it looks like quite the waste of resources: I mean, displaying loads of text in graphic mode. Why the effort when we have 80x25 text mode supported natively.

      Actually I experimented with those "hot key" resident programs, which you can use to interrupt and existing program, but I'm getting out of RAM (512kb) pretty soon as I try to put more things at my fingertips. Maybe once I upgrade to 1 MB it'll be better (though I can only use 640kb of it). Additionally, with a 20MB disk I'm already running out of space to store everything I need, let alone an entire book worth of text.

      -----------
      2. since all it has are concise explanations - you'll spend less time wallowing in stuff you don't care about (when you want is something concise)

      3. it is formatted specifically for quick syntax & example checks, rather than for general purpose documentation


      Yup, looking up larger manuals on a computer is very slow, much slower than manually browsing a book. There are those new 286 processors, but they are quite expensive yet, so I'll have to churn with my trusty 4MHz 8086 for now.

      -----------
      4. there are benefits to books - you can easily add comments to them, you more (sometimes) more easily scan for information, etc, etc.

      Ok you have a point here. It's very easy to add comments to books. I wish there was something like a common shared via network online MySQL manual, and it had a comments section on each page, consider the possibilities!

      They could call it something like "User Comments", and you'd never run out of space, and even be able to read wise tips from other users.

      But alas, it's 1985 and the Internet isn't even around the corner yet. So a book next to our IBM XT is our best option.

  13. A newer MySQL cheatsheet... by expo1892 · · Score: 1

    Visibone has just released a newer MySQL cheatsheet. I use the Visibone Browser Book a lot. Very convenient.

    1. Re:A newer MySQL cheatsheet... by Anonymous Coward · · Score: 0

      Word to the wise; do a search before you post next time. This is already higher up the page.

  14. Dead right by cortana · · Score: 1

    Truer words were never, erm, implied!

  15. MySQL Pocket Manuals in Plucker format by hacker · · Score: 1

    Of course, I have had the MySQL Manuals in "pocket" (Palm, mobile) format for quite some time... you can get them over here in Plucker format.

    I also have the PostgreSQL documentation in Plucker format as well.

    (Don't forget to check the rest of my mobile work if you're interested in some of the other custom conversions I've done: FreeBSD docs, PHP docs, Cygwin/CygwinX FAQ, and dozens of others).

  16. 96 pages??? by Puppet+Master · · Score: 1
    MySQL "POCKET" Reference... I'm not sure 96 pages will fit in my pocket very easily.

    --
    The day Microsoft creates a product that doesn't suck, it will be known as the Microsoft Vaccuum Cleaner!
  17. Bind variables by Anonymous Coward · · Score: 0

    Ha! ha! Bind variables.

    Snort.

  18. How about an index? by RoloDMonkey · · Score: 1
    I own this. My biggest problem is that, as a relative beginner, I don't always know which command I want. Here is the relevant part of the table of contents.

    ...
    Commands 30
    Rules of Precedence 67
    ...
    That's it. Thirty-six pages of commands, almost half the book, without a list of what those commands are, and no index. For me, this book is pretty much useless. I almost always end up going to the online documentation.
    --
    Long live the Speaker Bracelet
    Rolo D. Monkey