A couple of years back, I created WWW::Ohloh::API because it seemed to be a fun thing to do. And trust me, it was. But now, since I’m not using that module personally, I thought it would be a good idea to see if anyone would be willing to co-maintain it. Before I could do that, though, I had to deal with two little problems.
My impressions: Considering that this conference was the first one of its kind in Argentina, I have to say it was great. Small, but great. Not many people knew about the event, but the response was still pretty good. It was a 3-day event with plenty of technical discussions and sessions, and some other sessions came from companies who wanted to share experiences and impressions on what is coming for MySQL technologies.
First of all, if you are using NFS to store Oracle database data files, I strongly advise you to enable Oracle Direct NFS (DNFS) to access these files. However, if you are not using NFS, DNFS is probably not of interest to you, and you should stop reading here. But, if you want to set it up, let’s go!
A while ago, I was paged by a client having backup job failure. Doing my routine as usual, I started the investigation by looking at the job execution log. Connected to the box was a strange output. Here it is!
Sharing knowledge not only is beneficial to others, but also enhances one’s own knowledge and broadens the spectrum. Blogging is all about sharing and this Log Buffer Edition brings together some great blog posts from around the database arena.
Recently, I was upgrading a database from 188.8.131.52 to the current 184.108.40.206 version. The database was using ASM, but I should notify at the beginning that the configuration is for a Stand-Alone Server and not RAC. Basically, the first things to be done for this procedure are part of the following checklist…
Join Francisco Bordenave from Pythian’s MySQL team for a presentation on replication, old and new.
The traditional NoCOUG SQL challenge has been launched this year with a twist: In the wake of the “BigData” trend/buzz, it’s now been upgraded to a “SQL and/vs. NoSQL” challenge. I took on the challenge, treading through my SQL comfort zone and thinking of ways I could bend relational algebra to solve the wicked puzzle suggested this year.
What if we added a new field in the META.json — let’s call it x_help_wanted — that would contains all the different types of help a module maintainer could require? Positions like maintainer, co-maintainer, coder, translator, documentation, and tester. We could even have a Dist::Zilla plugin to populate that field for us.
This is going to be a short one, but I think the changes to GitStore are cool enough to deserve a little blog-squeal.