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
In the near future, the probability is close to zero. In the distant
future, I'll be dead, and posterity can do whatever they like... :-) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
once again proving... (Score:2)
I can't recommend MySQL for any new installations any more.
MySQL does a job and does it well.. (Score:3, Insightful)
I still use mysql for a lot of reasons
Don't go writing off mysql because it doesn't provide triggers or stored procedures - these are hardly requirements to qualify as a real RDBMS.
Its much improved support for full text indexing and transactions in version 4 means that it is up to the job for most tasks.
Should you need any more power - it is relatively easy to combine with postgres and pretty simle to migrate parts to Postgres.
When I worked in bristol we had MySQL and Postgres working together, we were moving parts of the system bit by bit to postgres from MySQL and it went very smoothly.
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;
Reply to This
Parent
Re:MySQL does a job and does it well.. (Score:2)
The problem is that there are certain business rules we simply can't (or shouldn't) get around without triggers and so MySQL is simply out of the question. Now, if MySQL adds these features (and they get good reviews) by the time we *do* switch, I'll be happy to look again. :)