What is Digg?Sponsored by Best Buy
Best Buy casts another employee in holiday campaign. view!
youtube.com/bestbuy0 - Jarice Brodie has done some cool things in his life. Next: Best Buy’s holiday campaign.
34 Comments
- b0wl0fud0n, on 10/12/2007, -1/+22List of cheat sheets (including the submitted one):
http://www.smashingmagazine.com/2006/10/30/cheat-sheet-round-up-ajax-css-latex-ruby/ - fak3r, on 10/12/2007, -2/+5This was posted here before, but it's worth repeating, it's very complete. For ~95% of what I do I have a much simpler list posted here:
http://fak3r.com/2006/05/18/mysql-cheat-sheet/ - quipo, on 10/12/2007, -1/+4Firebird SQL cheat sheet:
http://www.alberton.info/firebird_cheat_sheet.html
PostgreSQL cheat sheets:
http://www.alberton.info/postgresql_cheat_sheet.html
http://www.petefreitag.com/cheatsheets/postgresql/ - gharding, on 10/12/2007, -1/+4You should really be kicking yourself if you're still using the mysql extension in PHP. Get with the times, install PHP 5.1, and use PDO. Even a little abstraction is better than no abstraction. Too bad hardly anything is completely SQL99 compliant.
- prockcore, on 10/12/2007, -1/+4You can also use Pear:DB if you don't want to (or can't) recompile PHP.
- SuperSloth, on 10/12/2007, -2/+5If you need a cheat sheet for MySQL... you probably ought not to be developing a web app at all.
- prockcore, on 10/12/2007, -1/+3Actually, by using Pear:DB you can gain performance because on mysql5 it will use prepared statements.
That means you can prepare "insert into mytable (name,address) values (?,?);"
Then you can loop and run "execute ('bob','123 main st')" "execute ('frank','432 niam st')" and so on to do multiple inserts and updates.
It uses less bandwidth, and mysql only has to compile the statement once. You get the added bonus of protection against SQL injection. - erikuma, on 10/12/2007, -0/+1Nice cheat sheet, although it's not covering all of MySql 5.0 or 5.1 new nifty features.
- skankyBacon, on 10/12/2007, -0/+1I hadn't dugg you down, but now I have to, because I hate when people get all indignant about being dugg down. It happened; life goes on.
- TenebrousX, on 10/12/2007, -0/+1@ prockcore -
PHP can do prepared statements directly to MySQL as well. If you are making a web app for your system, I find it's best to just use direct MySQL statements - cbmeeks, on 10/12/2007, -0/+1I love cheat sheets.
Diggy from me.
In fact, I'm going to tattoo this sheet to my a$$.
Pictures here:
http://www.codershangout.com
Ok, last time I go for a lame plug...lmao - icoms, on 10/12/2007, -3/+4thank you
- bluenullity, on 10/12/2007, -1/+2Not true, Reread the slashdot post.
- kjm16, on 10/12/2007, -1/+2Is there some sort of complete noob's guide to MySQL out there?... I am very lazy... and stumb (stupid+dumb=stumb).
no joke - jondavis, on 10/12/2007, -0/+0Now there's another cheat sheet here:
http://insites.ingenesis.net/2007/04/11/mysql-reference-cheat-sheet/ - BillyG123, on 10/12/2007, -3/+3I guess he posted that since they just announced they're only supporting te Enterprise versions of RedHat & SUSE now.
More to the point though, I thought people get bitched at all the time for posting their own stuff here. I'll never understand the digg mantra. Back to my cave... - diecastbeatdown, on 10/12/2007, -1/+1dugg this a while back, it's a pretty good cheat sheet but still missing quite a bit. i printed it out and its still on my wall at work, mine has notes all over it.
- Nodren, on 10/12/2007, -1/+1great little cheat sheet. i realize the purpose of it is so you dont have to memorize all of the information on it.. but i'd recommend memorizing most of it anyway, especially the different types of columns. some of the stuff can be looked up on mysql's site when needed, but to become really efficiant at drawing up mysql queries, its best to memorize most of that stuff(which can happen fairly quickly through using a cheat sheet like this and writing alot of queries)
- inactive, on 10/12/2007, -0/+0...ok, so then I'll repeat myself without saying that I don't understand why people are digging me down (and then I'll digg you down). :-P
On a typical commercial web hosting platform -- PHP 4.x, MySQL 4.x, and Apache 1.x -- using native PHP MySQL functions is measurably faster than using PEAR:DB. There are performance benefits to PEAR:DB, yes, but they are nullified by the performance impact of not using the native functions, which are, after all, optimized for MySQL. - inactive, on 10/12/2007, -1/+1Why am I being dugg down? If you, like me, operate in the commercial web hosting world (I am both a service provider, and an avid client of my own services), then you're running PHP 4.x and MySQL 4.x. You're also running Apache 1.x (before anyone chimes in about being "behind the times"). PEAR:DB and any other abstraction layer is measurably slower. Using native functions allow you to take advantage of SQL optimization and caching that you otherwise don't have. The "performance benefit" of PEAR:DB is nullified by the performance sacrifice of not using compiled PHP/MySQL functionality, *both* of which must be taken into account. I rewrote my CMS to use native PHP/MySQL, after initially writing it with PEAR:DB, when I realized my mistake (and confirmed that I had made a mistake using PEAR:DB, by Googling for benchmarks).
- fak3r, on 10/12/2007, -1/+1I posted mine above: http://fak3r.com/2006/05/18/mysql-cheat-sheet/
- jwm0z, on 10/12/2007, -0/+0I think it's useless without UPDATE and INSERT syntax - the ones I always forget, not SELECT.
- thepearson, on 10/12/2007, -1/+0Respectfully, While I am all for cheat sheats. IMHO you cant really go past the official MySQL (Section 12 esp) and PHP documentation, ( http://dev.mysql.com/doc/refman/5.0/en/index.html , http://nz2.php.net/mysql ), I am sure a lot of time and effort is spent making these documents as easy as possible for beginners while still providing in-depth documentation for experienced DBA's and Developers, I can honestly say while there are tons of links and books available, you cant beat the official documentation. My first port of call anyways.
- csrster, on 10/12/2007, -2/+1wtf? Are you saying that MySql is peculiarly ill-adapted to web-apps? Or that anyone who doesn't already know MySql is clearly too ignorant to ever learn how to use it? Or that MySql-specific constructs are so intuitively obvious that a cheat sheet is unnecessary?
- inactive, on 10/12/2007, -3/+2Actually, I value performance more than I value the comfort of knowing my app will run on a bunch of products that I don't use. You take a hit for abstraction, which means using abstraction in an app requires justification.
- LoveJackDaniels, on 10/12/2007, -1/+0"More to the point though, I thought people get bitched at all the time for posting their own stuff here."
I'm pretty sure the original author wasn't the one who posted this link. - jull1234, on 10/12/2007, -4/+2I too love Jack Daniels. It is a fine whiskey product which mixes well with Coca Cola.
- maexus, on 10/12/2007, -5/+2Great cheat sheets.
- megaman2005, on 10/12/2007, -3/+0Cool....This is a good little cheat sheet.
- xShadoWxDrifTx, on 10/12/2007, -9/+4Useful cheatsheets, when it is needed
How is this one compared to others? - evilbeatfarmer, on 10/12/2007, -13/+8So I guess you diggers don't like web apps based on MySQL database back ends.. *cough* DIGG.COM*cough*craigslist.org*cough* and many others.
Maybe if I said 'MYSQL IS A SEKRIT APPLE PROJECT!@$" i'd get more thumbs ups? - fjc8, on 10/12/2007, -11/+5PostgreSQL is better.
- voidptr, on 10/12/2007, -14/+6My MySQL cheat sheet:
http://www.postgresql.org/docs/8.2/static/index.html - evilbeatfarmer, on 10/12/2007, -14/+5Is MySQL the best thing since sliced bread or what?
The Digg Toolbar for Firefox lets you Digg, submit content, and keep track of Digg even when you're not on the Digg site. Download the official 
© Digg Inc. 2009
— Content created and posted by Digg users is