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