Zachary Fox (from Alert Logic too) wrote a very good tutorial on how to run Selenium RC to execute unit tests in a team environment.
If you have multiple users running unit tests concurrently against the same Selenium RC server, some nasty things may happen. Zach explains how to properly setup multiple Selenium RC servers, so everyone can work on their own server.
I work on the MySQL Enterprise Tools team, formerly of MySQL and now with
Sun
Microsystems. The 2.0 version of the Enterprise Monitor is
well under way. As part of this, the Java server backend has been
refactored to utilize Spring and Hibernate. Honestly, I didn't know either one
of those technologies before starting this project. Oh, what a
fun road it has been...
A big draw for using an off-the-shelf ORM was so that we didn't
have to write our own (kind of bad and slightly wrong -- those
darn transactions) caching implementations for the custom one-off
ORM that existed previously. A lot of our internal meta-model is
very static, so …
Kickfire has announced (as of April 14th, 2008) record breaking
results in the TPC-H(tm) Price/Performance category at 300GB and
also in overall performance in the non-clustered category at
300GB.
You can find the official results here on the TPC(tm)
(Transaction Processing Performance Council) website:
http://www.tpc.org/tpch/results/tpch_price_perf_results.asp
http://www.tpc.org/tpch/results/tpch_price_perf_results.asp?resulttype=noncluster
While the amazingly low price of the Kickfire Database Appliance
2400 will grab you (only about twice the price of a typical 4U
MySQL database server) -- the amazing performance per watt is
truly incredible. The 3RU Kickfire appliance used in the 300GB
volume test consumes …
i was going to write some reactions to an observation that postgresql has no bug tracker and its discussion last week, but lost the spark and abandoned the post after a few days. but today i ran across a quote from linus torvalds that neatly sums up my thoughts:
We’ve always had some pending/unresolved issues, and I think that as our tracking gets better, there’s likely to be more of them. A number of bug-reports are either hard to reproduce (often including from the reporter) or end up without updates etc.
before there was a bug tracking system for mysql, there was a claim that all bugs were fixed in each release (or documented), and there has been a lot of pain in seeing how well that sort of claim stacks up against a actual …
[Read more]Two month have passed since the close of the Sun-MySQL-Deal, two months of uncertainty whether it's a good idea to join Sun or not but after consulting my ElePHPant, who read the 18 pages of the contract and related documents (including MySQL termination agreement, data privacy agreement, ...), I'm quite optimistic and look ahead to a sunny future. Therefore I'll be a true Sun employee as of tomorrow, May 1st.
connector/odbc 3.51.25 and 5.1.4 were released today. the new 5.1 release has been deemed “generally available,” which is our really ridiculous term for a non-alpha/beta/rc release.
it was the day for the connectors team to do releases — previews of connector/openoffice.org and pdo_mysqlnd made it out before us, and i believe that a connector/net release is in the wings.
yeah, it is all odbc, all the time here, it seems. that is just because i can’t write about the really exciting stuff. soon!
that is not to say that releasing mysql connector/odbc 5.1.3-rc is not a huge milestone! it took us a while to get there, but we finally have a unicode-aware odbc driver that is, in our opinions, production-ready. now we just need some community feedback to find out if we are right. there are a few minor issues we know about already, but the impact of those is generally small enough that the majority of folks should not have any problems.
yeah, it is all odbc, all the time here, it seems. that is just
because i can’t write about the really exciting stuff.
soon!
that is not to say that releasing
mysql connector/odbc 5.1.3-rc is not a huge milestone! it
took us a while to get there, but we finally have a unicode-aware
odbc driver that is, in our opinions, production-ready. now we
just need some community feedback to find out if we are right.
there are a few minor issues we know about already, but the
impact of those is generally small enough that the majority of
folks should not have any problems.
Last November, I became an employee of MySQL Inc, which was owned
by MySQB AB.
A few weeks ago, MySQL AB and MySQL Inc etc et al became wholly
owned by Sun Microsystems, which immediately started rapidly
digesting this new corporate M&A meal.
As of today, I am now an employee of Sun Microsystems.
For the most part, for the time being, nothing changes. I do the
same kind of work, have the same lovely workplace (an array of
local cafes), and the same annoying business travel. (And the
same expense reporting "system". Ugh!)
We shall see what does change, next.
But for now, when someone asks me what my job is, my short answer
will remain "I work on MySQL".
the march of progress continues, with the release of mysql connector/odbc 3.51.24. we are down to 33 bugs, most of which will not get fixed further 3.51 releases, but will be fixed in 5.1 or later. i think the two remaining issues we might fix in 3.51 are the crashes of the setup library on mac os x (which may just require a 10.5 build) and bug #12805.