I have a copy of "Programming the Perl DBI" and its certainly still relevant. You don't say whether or not you have experience with SQL, but you will quickly need to tangle with it. I recommend "Learning SQL" by Alan Beaulieu. This book starts from ground zero and uses MySQL for the examples using the mySQL command tool.
Update: RE: moving from "flat files" to DB... The DBD-CSV module is a pretty good step to using SQL with the Perl DBI while accessing the CSV flat file format that we both love and hate. CSV is loved because of its seeming simplicity and hated because of the tricky details (like commas within quotes: "some text, that is one thing but has a comma"). Get the basics of SQL. That knowledge translates very directly into DBI syntax. But since the .CSV format is text, it is very easy to see what your DBI SQL statements actually did to the DB.
BTW,Some of the DB's that I use export their "CSV" data using the pipe "|" instead of a comma ",". Excel can understand that format. So "CSV", "Comma Separated Value" can use a different field separator than ",". Keep that in mind when generating CSV files.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
