When your favourite ex yahoo employee and mysql guru blogs about a "dns problem" and how he solved it using Twitter you can only smile ;) At last some useful use for Twitter .. when it's up at least ..
The future of commercial open source software lies in commercial licensing strategies, but which are the strategies that are more likely to deliver the results vendors are looking for?
Much of the open source blog chatter over the Christmas period was related to open source business models/strategies, largely triggered by a post written by Dave Rosenberg in which he declared that commercial licensing, and specifically open core licensing will be all the rage in 2009:
“Typically we now see an “open core” freely available with “exclusive” or proprietary features only available when you pay. If you are trying to build a commercial business on top of an open source project, this is likely the right answer.”
…
[Read more]
So, my Haystacks teammate Brian DeShong tagged me in his list of
seven. We won
that trivia contest by the way. It was a real team
effort.
So, here goes my seven things:
- I have six kids. Okay, let that sink in. Yes, six. Logan(12), Macy(11), Molly(9), Parker(7), Collin(3), and Hudson(6 months). I know what causes it. Yes, it is hard at times. But, there are those moments when you are sitting in the yard or in the den and all is right in the world. The best program I will ever write will not compare to what have done with my children. They are truly my greatest project. My wonderful wife blogs about them at Moonmania.
- I started my career as a Visual Basic programmer. PHP and VB are very much alike. …
Installing MySQL is quite an easy thing to do, especially when done using pkgs, dmgs or exes. It gets just a tad more time consuming and brain intensive when installing a .tar.gz binary package. It is when you’re compiling MySQL source directly that you’ll need some planning and playing, but the latter is only done in particular cases such as when you’ll need a particular engine not shipped with a pre-compiled package etc.
Today we’re going through the steps required for a typical MySQL installation from a .tar.gz package on a *nix based platform, including the download, installation, configuration and securing.
Steps involved:
1. Download MySQL binary tarball from mysql.com
2. Create a folder structure where the installation will be
held.
3. Install the package
4. Secure the installation
Step 1: Download MySQL
Go to http://dev.mysql.com/downloads/ and choose the particular …
[Read more]
Friday, I helped a friend who is working a MySQL gig to optimize
a query that should have been way fast, but was taking about 100
seconds. Brian even took a look and helped with it. I learned
today what the real problem was. The whole system was running on
a single ec2-small instance. And by "whole system", I mean a test
mysql server, the production mysql server, a test apache server,
and the production apache server. All on one ec2-small.
Talk about doing it wrong.
TIMESTAMP is interesting in that it can give you an easy way of keeping track of when was the last time a row was modified, with a few caveats, listed below. The tests were run on 5.1.30-community MySQL Community Server (GPL).
- By default, TIMESTAMP is NOT NULL. Inserting a NULL value
causes it to store the current DATETIME;
mysql> CREATE TABLE t1 (c1 TIMESTAMP); Query OK, 0 rows affected (0.11 sec) mysql> INSERT INTO t1 VALUES (NULL); Query OK, 1 row affected (0.03 sec) mysql> SELECT * FROM t1; +---------------------+ | c1 | +---------------------+ | 2008-12-30 20:42:25 | +---------------------+ 1 row in set (0.00 sec) mysql> CREATE TABLE t2 (c1 TIMESTAMP, c2 TIMESTAMP); Query OK, 0 rows affected (0.06 sec) mysql> INSERT INTO t2 VALUES (NULL, NULL); Query OK, 1 row affected (0.02 sec) mysql> SELECT * FROM t2; +---------------------+---------------------+ | c1 | c2 | …
I spent the last two weeks offline in the Indian Ocean (not all the time as literally as in the picture on the left, though). This triggered a bit of long term thinking and observations, some of which I’ve already published my ten New Year Resolutions in Swedish, in German and in English, respectively. Some of these are purely private, many are inspired by work at MySQL and Sun.
I won’t spam Planet MySQL with all of the resolutions, but here’s an excerpt to tease you into reading the actual blog entry: …
[Read more]
Listening to Sheeri's presentation on MySQL 5.1, I saw that
there are a few questions left unanswered. I am listing here some
of the questions that I found interesting, plus a few from an
early webinar on the same topic.
- Q: does Partitioning physically split data?
- A: No. Some engines (MyISAM, Archive) do a physical split, but this is not necessary, as you see if you apply partitioning to a InnoDB table. Partitioning is a logical split of data, for easy retrieval. It is completely transparent to the user.
- Q: Can you set partitions to different servers?
- A: No. Partitions are logical parts of one table within one server. Partitioning through the Federated engine is not supported.
- Q: How efficient are Row-Based …
Since Kore, Lars and Marcus forced me to write this:
- Sebastian's first foreign language was Latin, for me Latin was the reason to start programming (by trying to hack the vocabulary trainer my brother wrote, so I learned Basic instead of Latin)
- I started PHP since I was too dumb to get my Perl CGI scripts working after our home server crashed
- I still have more Perl books than PHP books
- Compiling PHP 4.0 on our Pentium 90 home server took a night or so - and often forgot to activate some …
MyISAM InnoDB Default since version 3.23 Relatively newer Files storage: FRM: table definition, MYD: Actual Data MYI: Index File FRM: table definition .ibd file (concept of table space) or single…
The post Difference MyISAM and InnoDB Storage Engines Mysql first appeared on Change Is Inevitable.