|Problems? Is your data what you think it is?|
Re^2: Perl and Databaseby afoken (Parson)
|on Aug 22, 2009 at 17:04 UTC||Need Help??|
I would recommend NOT to start with MySQL. It often behaves very different from most other databases. (This is not an evil plan, just optimizations for special cases in some applications. And annoying in all other applications.) Good documentation.
Oracle is nice, if you have a good DB admin that manages it for you. Everything seems to be documented, even Larry Ellison's coffee mug. You just have to know where to search for the documentation. And Oracle brings TONS of software, including Apache, Perl, Java and every tool you can think of. Bloatware.
MS SQL is easy to set up (just click the "continue" buttons until they disappear ...), but it can be a real PITA when it comes to concurrent access, locking, multiple active statements, and access from non-Windows systems.
PostgreSQL is easy to set up, clean, well documented, and it has a very short gotchas list. (And for me, it feels like Oracle done right.)
SQLite is small, low-fat, and can easily be embedded. But it has a very unusual type system.
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)