It sounds like your current version is similar to Ima::DBI, which is the basis for Class::DBI
so your transition could be quite easy. I'm a fan
of Class::DBI and have tried Alzabo (which I suspect
Class::DBI is evolving into, they just added column
objects). I think Alzabo tries to do too much, YMMV.
I use MySQL with Innodb tables when I can, I just
need transactions. That's when I can't ditch the
RDBMS entirely. There seems to be such a mismatch
between schema oriented and strongly-type databases
and Perl.
Regarding stored procedures vs perl logic, read
Domain Logic and SQL for a language neutral consideration of the problem.
The article points out a few cases where you'd want to
go one way or the other but boils down to
"Choose based on your company resources and culture"
-
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.
|