Sorry for the typo.

Just to clarify what I want to achieve:

I have objects containing other objects (Bubbas containing several Hubbas in the above).

What I want to do now is to load the whole object (or object-graph if you want) from the database and then do some processing on it.

The processing consists of the container-object receiving a message (which comes from a queue) which it then passes on to some of the contained objects which in turn may have to inform the container about something in the course of their processing the message.

After all this processing is done (the whole graph is updated) I then want to store the whole graph again in one transaction (which also will contain the dequeuing of the message).

My problem really is that I don't have a good understanding about the intention of the several DBIx::Class components and the whole underlying philosophy (e.g. naively I had assumed that the framework would assure that you only ever could have one instance per primary key but that does not seem to be the case...)

And I have used DBI a lot and fully agree with what you say regarding the advantages of a proper ORM-framework, I just wish I would understand it...

But many thanks

In reply to Re^4: Looking for DBIx::Class tutorials and examples by morgon
in thread Looking for DBIx::Class tutorials and examples by morgon

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.