My usual apprach is to have value objects that can be loaded or saved to a datastore, ie:
$datastore->beginTransaction();
my $person = $datastore->getPersonById($personid);
...manipulate $person...
$datastore->store($person);
$datastore->commitTransaction();
The main advantages of this is:
- Simplicity: The CRUD approach (Create, Retrieve, Update, Delete) is well understood and aligns well with SQL
- Performance: Access to the datastore is kept to a minimum
- Modularity: The datastore is decoupled from the value objects
I feel it's usually best to leave transaction management to the datastore, rather than trying to hack together something yourself.
-- Michael Snell
-- michael@snell.com
-
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.
|