comment on

This is a node that has really touched on the issues that have made me disinclined to go down the CDBI route. But i have to admit i'd really like to hear you summarize this more cogently. I did do a search on Fabian Pascal but I think an article on the subject by yourself would be a very worthy meditation.

All I can say is that every time ive looked into CDBI it seems appropriate for fairly naive DB's but for serious work it seems totally unsuitable for handling complex relationships and business logic. Your comment about object/record class/table mappings really seems to encapsulate the problems I have. Its extremely unusal for me to have any such mapping, in fact its much more common to have objects be represented as a derived amalgamation of many records from many tables.

Anyway, I really hope you meditate on this.

---
demerphq

_{First they ignore you, then they laugh at you, then they fight you, then you win.

-- Gandhi}

In reply to Re^2: Class::DBI not intuitive by demerphq
in thread Class::DBI not intuitive 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.


The stupid question is the question not asked
	PerlMonks