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].
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!
Shiny! (Score:2)
What forced the switch from Postgres? Even worse, why MyISAM? I assume there's a compelling story in there somewhere :)
Re: (Score:1)
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.
Re: (Score:2)
Nice, but invalid? (Score:1)