A quiz, in 4 parts:
Given the following table definition in the sakila
database:
(more…)
A quiz, in 4 parts:
Given the following table definition in the sakila
database:
(more…)
MySQL 5.1 release as "GA" seems to be the most controversial to date. It had very negative response from Monty, original MySQL Founder and controversial responses in community including another beating by Kevin Burton.
There is also very interesting reading on MySQL 5.1 open bugs
So how do I take it and where do I think MySQL 5.1 Quality Stands ?
I've been MySQL user for years since version 3.22 and when MySQL 3.23 came out we were using it in production since 3.23.3 or so, when it was in the Alpha stage still. A lot of bugs were fixed after we started using it... we just made sure the bugs which are important for us are fixed. Later while working …
[Read more]With all the furor over MySQL 5.1 GA, its release schedule, its quality, etc etc I think a fundamental claim is being left un-examined. Lots of people are saying that if you leave out the new features in 5.1 and look only at the features that existed in 5.0, it’s better quality. The implication is that the process of building 5.1 looked like this: rip out nasty code and fix it all up, so there’s a brand new architecture free of code debt.
Having worked on previous incarnations of Glassfish clustering, I can tell you this is no easy feat. Watch the video, it will only take you 10 minutes :)Here's a summary of the timing
http://blogs.sun.com/jclingan/entry/glassfish_clustering_in_under_10
I am very proud to announce that so far, two proposal I submitted
for the MySQL Conference 2009 have been approved! Wohoo!
(Did you submit a proposal too, and you still didn't receive a
reply? No worries - there is a massive amount of proposals to go
through. From past years experience I can say - Don't despair,
just have some patience. It can take some time for the MySQL
community guys to work though all the proposals.)
As every year, I am looking forward to this event a lot, and
having the opportunity to speak there just brings a big smile to
my face ;)
Anyway - These are the approved proposals:
The first proposal is for a 45 minute …
Petr Pisl is presently posting a PHP picture a day - how's that for alliteration. I like this one - place your cursor on the function keyword and all places where you return from the function are highlighted. I can imagine that being very useful...
Funny that I'm seeing so many of these. We will be providing this as part of the next release of NetBeans. We'll also be supporting export to XML, import from CSV and also import from another table.
I know there are other tools out there that do this as well. If it were me, I'd much rather have a tool like NetBeans do it than write a script like this...
http://www.total-php.com/article/15/creating-a-text-or-csv-file-of-information-from-your-database/
In two separate instances, prepared statements used up all my
database's connections and completely locked it. To the point
that we had to restart the mysql server and in the other case,
physically reset the server (not something you usually do with
linux servers).
Apparently, one table had a read lock on it, which made the
prepared statement wait a bit too long and it decided to flood
the database connections till it would got an answer. Only the
table was still locked and the database came to a screeching
halt. The last thing I saw on my screen was a bunch of the same
prepared statement on my process list screen, completely taking
up all the slots and then.... I lost my connection to see the
process list.
I don't really understand how the perl script and php page that
ran the prepared statement could be so aggressive or where was it
defined to continue opening new connections till they got an
answer.
This is definatly …
Here is a summary about Disk Data tables in MySQL Cluster.
Data node configuration:
SharedGlobalMemory=384MSharedGlobalMemory in
mysqlcluster-63/cluster/config/config.ini before you start the
cluster.DiskPageBufferMemory=3072MBDiskPageBufferMemory in …
Working at Sun was my first acquisition experience. I guess it
was what I expected; managers hyping it up about being a "perfect
match", and how much the two companies had in common. It was kind
of interesting to see this even turned up a notch after they
received additional "Sun management training". Anyway, I
digress....
I'll state upfront I consider my experience a bad one (but I'll
save the personal stories for another day). Here was an issue I
saw while training Sun staff on how to user MySQL:
Sun's has a conflict of interest in selling hardware.
MySQL (InnoDB) doesn't actually *work* on big computers. It only
scales up to about 4-8 CPU cores, and then it hits all sorts of
internal bottlenecks. Most architectures work around this by
using many small machines rather than one big one (aka "scale
out").
But for Sun the profits are larger on selling *bigger* hardware.
Most of Sun's bigger …