I didn’t take any photos myself at the MySQL User’s Conference. In reflection, perhaps I should. I did make it into some photos however. A few of them here.
Stolen from Jeremy Cole’s Photos at http://jcole.us/gallery/uc2006
I didn’t take any photos myself at the MySQL User’s Conference. In reflection, perhaps I should. I did make it into some photos however. A few of them here.
Stolen from Jeremy Cole’s Photos at http://jcole.us/gallery/uc2006
This post recorded mid-day on Friday.
The MySQL User conference has ended and I find myself waiting for my flight home — a good time to gather thoughts.
I personally think the conference was a great success. We had over 1500 attendees and the feedback I heard on the conference was very positive. I did hear a few asking for the sessions to be longer than 45 minutes and I do agree that 45 minutes can be a bit cramped, especially for a speaker who is re-using a session previously delivered in a longer block, but overall the response was great.
I had three sessions this year, and those sessions seemed well received by the attendees I spoke to. I am *very* glad that I backed up my slides to a keychain drive and ghosted my drives before leaving as it made the crashing of my laptop an annoyance rather than an unmitigated disaster. I worry that the distraction of a laptop crash may have left me at less than 100% for my sessions …
[Read more]Update: High Res Versions at http://www.openwin.org/mike/wordpress/wp-gallery2.php?g2_view=core.ShowItem&g2_itemId=1198
This year there was a nice little bonus, Julian Cash was on hand to take photos of the staff with a proper studio setup. I’ve seen some of his work before and liked it, and was looking forward to a session. When the photo sessions were announced, we were asked to bring a prop that represented ourselves or our work or personality. I actually forgot about the prop requirement but went for a session on the way to my Hierarchy talk and walked in carrying a stack of books to give away. Julian took one look and pronounced ‘Great Prop!’ upon seeing my stack of books. It was not planned as a prop, but seeing as I am a technical writer and …
[Read more]
I would like to thank everybody for a very successful MySQL Users
Conference 2006! I've been told there were over 1600 people,
that's absolutely fantastic and an increase of over 30% from last
year.
Those numbers are very nice of course, but I reckon it's been
successful because attendees have told me it was. That's the most
important benchmark. Naturally, there's also constructive
feedback which we can use for next year. The above map gives an
indication of where attendees came from.
A special thanks to Jay Pipes for sharing some of my program
chair responsibilities, which greatly improved my level of sanity
(quite a few of you noticed that I was more relaxed on-site -
this was a key reason). And to Colin Charles, who took on
numerous tasks involving chasing after people and just getting
stuff done independently.
…
I have written before about using joins instead of subqueries, especially for NOT IN queries, which can usually be rewritten as exclusion joins – sometimes with huge efficiency gains. In this article I’ll look more closely at the performance characteristics of a few queries I’ve optimized in MySQL 5.0.3. I’ll also show you some tricks you can use to get MySQL to optimize queries better when you know it’s being inefficient.
There could be many reasons why a connection to MySQL server can fail, like
Of all the errors, this thread will discuss Maximum
Connection Errors.
This particular parameter max_connect_errors defines the
no. of connection errors a particular host can make before it is
banned. Yes Banned! This is a feature that MySQL provides
to limit erroneous clients.
There could be many reasons why a connection to MySQL server can fail, like
Of all the errors, this thread will discuss Maximum
Connection Errors.
This particular parameter max_connect_errors defines the
no. of connection errors a particular host can make before it is
banned. Yes Banned! This is a feature that MySQL provides
to limit erroneous clients.
MySQL will allow n number of connections at a given point of time, To find out that n no of connections run the following command.
mysql> show variables like 'max_connections'; +-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | max_connections | 100 | +-----------------+-------+ 1 row in set (0.00 sec)
So this server will allow max of 100 connections at any given point of time.
MySQL will allow n number of connections at a given point of time, To find out that n no of connections run the following command.
mysql> show variables like 'max_connections'; +-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | max_connections | 100 | +-----------------+-------+ 1 row in set (0.00 sec)
So this server will allow max of 100 connections at any given point of time.
Tomorrow morning at 7:30 AM I will be leaving from Monterey for
San Francisco where we (me and Michelle) will be catching a
flight to Atlanta at noon. We will arrive in Atlanta around 8:00
PM EST. I believe we will have the shortest day ever due to the
time difference.
I am really thankful to MySQL and especially Arjen and Jay for
inviting me to speak at the MySQL Users Conference. I enjoyed it
a lot and will miss everyone I met until we meet again. Thank you
everyone for such a great time.
Frank
MySQLUC