MySQL Conference User and contacting me


MySQL Conference & Expo 2008



Hi,

I don't get out here too often. If you have a question, or comment, please feel free to post it here, but also send it directly to me @ jmiller@mysql.com. You will get a faster response.

Best wishes,
/Jeb

Comments

Post a Comment

Popular posts from this blog

MySQL Cluster Replication

MySQL QA In the 5.1 release MySQL Cluster will support replication to another MySQL installation. The replication is handled using Row Bases Replication instead of Statement Based Replication. I have been testing it for about a year now and it has gotten really hard for me to break at this point, but I am still trying. So what is so cool about Cluster Replication? Good question! One answer: Cluster Replication really gives a company five 9's (99.999%) in up time. You can have a Master Cluster in the main site supporting the business and have another Slave Cluster in a total different site that can be used as a backup for times there are issues with main site. In addition, the Slave Cluster can also be used for reporting or data mining to take that traffic off of the main Cluster. How hard is it to setup? Another great question. Answer: Easy So to set it up, you would create two set of Clusters configured the way that you wanted them. You configure the Master MySQLD to create a bin ...
Read more

New MySQL System QA blog

Hi, It has been a while since I last posted, but I wanted to post about my teams NEW blog page. New System QA Blog As always, we look for ways to improve QA and your feedback is always welcomed. Best Wishes, /Jeb
Read more

Perl IO::Socket, how to make them talk on both ends Cient/Server

Hi, Was exploring IO::Socket for some test automation I'm looking at doing. I found a lot of examples on talking to the server side, but not really any good ones on how to recieve and process on the client side what the sever sent in response. After playing with it for a while today, I finially got the basics working and wanted to share incase others are wanting to deal with 2 way comunication. The main thing to remember is the $_ and what it is used for. Examples: Cleint Side: ----------- use IO::Socket; $sock = new IO::Socket::INET( PeerAddr => "127.0.0.1", PeerPort => 1234, Proto => 'tcp') || die "Error creating socket: $!"; print $sock "test\n"; #test coms and start a chat while ( ){ print "$_"; # The servers reponse will be in $_ if ($_ ne "MySQLD is now down\n"){ print $sock "shutdown\n"; } else{ print $sock "exit\n"; } } close($so...
Read more