Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

domm (4030)

domm
  (email not shown publicly)
http://domm.plix.at/

Just in case you like to know, I'm currently full-time father of 2 kids, half-time Perl hacker, sort-of DJ, bicyclist, no longer dreadlocked and 33 years old

I'm also head of Vienna.pm [pm.org], maintainer of the CPANTS [perl.org] project, member of the TPF Grants Commitee [perlfoundation.org] and the YAPC Europe Foundation [yapceurope.org].

I've got stuff on CPAN [cpan.org], held various talks [domm.plix.at] and organised YAPC::Europe 2007 in Vienna [yapceurope.org].

Journal of domm (4030)

Friday April 09, 2010
01:58 AM

oe1.orf.at relaunch done

[ #40304 ]

The new and shiny oe1.orf.at is finally online!

As you might expect it's crafted using the finest ingredients of Modern Perl: Catalyst, DBIx::Class, Moose, HTML::FormHandler, KinoSearch. Relaunching the site was a nice project, even though there were some setbacks:

I was forced to switch from Postgres to MySQL (using - the horrors - MyISAM), so I couldn't use any real database features like transactions and referential integrity; the launch date was postponed a few times, so I couldn't help organising the QA Hackathon as much as I wanted (in fact I can also not attend all days, because I want to spend some time with my family before leaving for Berlin / Icleand).

Anyway, after fixing some last post-deployment glitches everything seems to work now. Yay!

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • What forced the switch from Postgres? Even worse, why MyISAM? I assume there's a compelling story in there somewhere :)

    • It seems to me if one were to have good reason to pick MySQL, then it would necessarily be for MyISAM. That engine is at least compelling insofar as it is essentially a NoSQL database with an SQL frontend. For mostly-read workloads it’s an interesting option.

      In contrast, InnoDB is just a crippled wannabe regular transactional RDBMS. There are far better choices if you need one of those. InnoDB only ever makes sense to use when you are stuck with MySQL as an a priori constraint.

    • Because they didn't want to support another database. They are using Oracle and MySQL, and that's it. I was lobbying for Postgres, but in the end the corporate policy won. I can see their point, but it was still painful...