comment on

I my experience, as soon as you grow beyond using the database as a way of just storing simple data, you will have joins in most of your queries, and so very little use for Class::DBI and related socalled simple tools.

Class::DBI is great if you see it as an SQL based object persistence framework. If you try to use it as a replacement for SQL itself, it suddenly becomes a whole lot less useful. It's not a querying language - in fact, that is what it tries very hard to not be :)

About so-called "simple" tools, I'm sure you will find that a simple interface can very well be used in complex designs, having looked at DBIx::Simple. It doesn't abstract, it simplifies. Please don't see one as the synonym of the other.

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

In reply to Re: Maybe too simple by Juerd
in thread RFC: Simple DBI abstraction by Jaap

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.


Clear questions and runnable code get the best and fastest answer
	PerlMonks