IMO, database abstraction is useful. But, mapping tables to Perl classes isn't any abstraction at all. It's exposing the details of your database layout to your program - quite the opposite of abstraction.
I've seen the following design a few times, and it's my favourite:
+------+ +------+ +------+
| App. | | App. | | App. | ....
+------+ +------+ +------+
+----------------------------+
| Shared application library |
+----------------------------+
+----------------------------+
| Database Interface Library |
+----------------------------+
Application
------------------------------------------------------------
Database
+--------------+ +--------------+
| Stored Proc. | | Stored Proc. | ....
+--------------+ +--------------+
+-------+ +-------+ +-------+
| Table | | Table | | Table | ....
+-------+ +-------+ +-------+
Each layer only talks to the layers directly above or below it. Perhaps overkill for a simple web application, and maybe not suitable for an agile environment, but the application not knowing anything about the table structure gives more freedom than one initially would think.
-
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.
|
