Posts Categorized: Perl
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, let’s have a look.
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.
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.
The actual challenge calls for a more generic solution than originally described in the magazine. Because there is no glory in half-solving a problem, I had to come back to it. And because the Great Karmic Balance could probably use it, I thought I could take advance of the broader scope to produces a solution more geared toward elegance and modernism.
In the last few weeks, I launched quite a few small releases to CPAN. Taken separately, they are hardly worth a full blog entry, but taken together, they’ll make for a lovely N&I entry. So if you have been wondering what I’ve been up recently, here goes:
So NoCOUG announced its third international SQL & NoSQL challenge (look at page 25 of that pdf) earlier this week. Yay! As I did last year, I tried my hand at forging a Perl solution for the challenge. Just for, y’know, peer-pressuring a little my colleagues into entering the fray.As it happens, this week is a little.. intense, $work-wise, so I wasn’t able to polish my solution into pure howling madness. But I daresay the work-in-progress that I have is still worth a few cackles. Although you shouldn’t take my word for it. Here, I’ll let you be the judge of it.
At $work we have a need for a little job daemon that would poll jobs and process them. But there is more than one type of job, so the solution that we need will have to be a little more complex. To get to my goal, I decided that I would have a generic Poller class. For each type of job to monitor and run, I will create a different object with parameters to tell it how often to poll, how to poll and what to do with the stuff it poll. Sounds good? Perfect, then let’s go.
These days, to craft basic emails, I go with Email::Simple. For the more heavy stuff with attachements and what-nots, I reach out for Email::MIME. Together, they make a pretty awesome duo. But… (come on, admit it, you knew there was going to be a ‘but’)
Our flagship tool, Support Track, is steadily migrating over to use DBIx::Class to read and manipulate our databases. This is a very useful tool, for many reasons which many people explain better than I could. One of those reasons is that — thanks to the magic of SQLite — it lets us write unit test scripts, and other quick prototyping code, without needing to set up a heavy database server to run against. However, Support Track is powered by Oracle, not SQLite, and while DBIx::Class abstracts most of the differences out of our code, it can’t completely eliminate them. How do we overcome the syntactic differences?
Recent Comments