In my experience I would say that you should NOT go with PERL to do any of your DB work. I am doing exactly what you want to do (Extracting XML and building XML files and inserting them in to the DB). PERL has an especially difficult time interfacing with PostGRES and there are currently some bugs and efficiency issues in the existing CPAN modules that might allow you to do this.
My suggestion is that you use C to make a database abstraction layer, where all your logic and database calls are made through C. All your server-side programming can be done through PERL (because perl is excellent when it comes to working with verbose data) making function calls to your C API. You should never have to write any SQL in the perl (just DB function calls defined in your C).
This has proven to be a very efficient and ultimately time-saving process. It has also helped in debugging and optimizing our DB performance.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.