[Deprecated] DMZ 1.5.3 (DataMapper OverZealous Edition)

[eluser]OverZealous[/eluser]
@NachoF
Short answer, no. I recommend that you relate Clients directly to Payments, and keep track of them that way. It looks like, from the names, these are written to but not updated. Since every Payment has a single Client, just add client_id to your Payments table, and add the Client whenever you INSERT a payment.

Longer answer:
Yes, you can, but you have to basically write your query by hand. And you'll probably end up with weird duplications, due to the many-to-many between Receipts and Payments.
How I have done that, before I wrote DMZ, is to use this trick:

Code:

// note: adding the joins directly to the DB class
$payments->db->join('payments_receipts', 'payments.id = payment_receipts.payment_id');
$payments->db->join('receipts', 'receipts.id = payment_receipts.receipt_id');
$payments->db->join('events', 'receipts.event_id = events.id');
$payments->where('events.client_id', $client->id);
$payments->distinct()->get();

However, I highly recommend against this. It becomes hard to maintain and it's awkward to read. Storing the client_id on Payments will also be an order of magnitude (or two) faster to query.

Also, I'm curious why payments are many-to-many to receipts? There can be more than one receipt per payment?

Finally, you should go back and edit (delete with a note) your comment on the DM 1.6.0 board, to avoid cross-posting.