Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

Re: Perl and Database

by dHarry (Abbot)
on Aug 20, 2009 at 07:28 UTC ( #790017=note: print w/ replies, xml ) Need Help??


in reply to Perl and Database

Just start with mySQL. Easy to install and maintain. It's a very popular database also with other programming/script languages. The other databases you list are high-end products and often cost you money. You might also want to spend some time on data modeling and SQL in general.


Comment on Re: Perl and Database
Re^2: Perl and Database
by Tanktalus (Canon) on Aug 20, 2009 at 17:14 UTC

    FYI: Most of the "high-end" DBs come in free versions. SQL Server, Oracle, and DB2 (which wasn't on the original list, but is what we use - and what I use as the back-end to the CB stats page) all have free versions (not to be confused, of course, with open-source). I suspect that the official support is the same, too: none. But I've got a lot of help on forums, usenet, and IRC, so no complaints so far.

Re^2: Perl and Database
by afoken (Parson) on Aug 22, 2009 at 17:04 UTC

    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.

    My recommendations:

    • For fun projects as well as for new commercial projects, I would recommend to use PostgreSQL.
    • If you want to learn more, learn Oracle, then MS SQL, followed by MySQL and SQLite. (Clean to dirty order.)
    • If you have to deal with web hosting, you should learn MySQL (available nearly everywhere, but often in ancient versions) and SQLite (for hosters unwilling to provide a usable database), remembering that they have unusual behaviours.
    • If you want to earn money, you should know all of them, including the "light" versions (SQL Express, Personal Oracle). You sould also try to learn DB2 and other RBDMS.

    Alexander

    --
    Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://790017]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (5)
As of 2014-12-29 00:39 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (183 votes), past polls