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.
I played with Mongo and looked at Mongoose, which are nifty, but holy schmolee are Mongo databases huge. And then I re-discovered DBIx::NoSQL, which was pretty much smack what I wanted. But I needed a way to easily serialize my objects for it. So I dragged in MooseX::Storage to the mix. And then I had fun with helper classes and roles to make the interfacing between the two systems as smooth and slick as a buttered piglet.
With the rapid advancement in the database technologies, the legacy systems are either being upgraded or replaced. Or, in some cases, technologists are finding ways to support them in new ways, showing us the flexible nature of databases and the belief of professionals that the sky is the limit. For this Log Buffer Edition, we go even beyond.
A new trial version of DBD::Oracle has been churned out. This release is mostly about Martin J. Evans going all ninjawesome on minor bug fixes as well as paving the way for an upcoming refactoring/speed boost of ora_verbose. As usual, the new version will be soaked for at least 2 weeks before it will turn into its fit-for-general-consumption v1.46 incarnation. Testers, please give this baby a whirl. The full changelog follows for the curious-minded.
I’ve rewritten this blog post in the series to include other new features in SQL Server 2012 outside of high availability and disaster recovery. Ever since the product has been released, I’ve had a chance to look at features that will address performance challenges and business intelligence requirements.
We have a few clients already using Enterprise Manager 12c Cloud Control. The interface and navigation have improved a lot from the 11g version in my opinion. However, as with any new release of anything, quite a few bugs still need to be fixed. After working with Oracle on some of these bugs last week, we were asked to apply the Bundle Patch 1 (BP1) to one of our clients’ installation. The first thing that I noticed when I started looking for information about BP1 was the amount of warnings from different people I found in MOS and around the internet.
Here is the latest MySQL news.
The Ottawa Oracle User Group (OOUG) was kind enough to invite me to give presentations for a whole morning. The group was ultra engaged and asked a lot of good questions, so my usual 50-minute Big Data presentation ended up taking 100 minutes, and the rest of the content had to be squeezed a bit. I hope everyone had a good time!