Well the ORM side is about the same kind of philosophy Phil is talking about. Use only a common denominator subset of many database engines, add it a few best practices and you get closer to the goal of an ORM. Also once you have started hiding the actual database (to the point it does not matter what it is!), you can start thinking about even more powerful abstractions.
The other day I came across DBIx::Perlish and wondered if it was another full-fledged ORM...still there was that 'perlish'. The author addresses just that in the docs.
cheers
--stephan
-
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.
|