• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Deprecated] DMZ 1.5.3 (DataMapper OverZealous Edition)

#1
[eluser]OverZealous[/eluser]
This is an outdated version. Please see the newer version here.

Thanks goes to stensi, for providing such an amazing code base to work on.

DataMapper OverZealous Edition 1.5.3

DataMapper (DM) is an Object-Relational Mapper that builds on ActiveRecord. Data is loaded from database tables into objects, and relationships can be managed through simple, easy-to-read functions.

DataMapper OverZealous Edition (DMZ) adds several important features to DM, enhancing it's usage, usually without requiring any code changes.

To install DMZ over DataMapper, the (fairly simple) upgrade process is described here.

DMZ offers these features and more over the original DataMapper:
In-table foreign keys
Multiple relationships to the same model
Better self references
Add fields from a related model into one query
Update, view, and query extra columns on join tables
A shareable extension mechanism, including:
Easy creation of HTML forms,
Processing posted input,
Converting to-and-from JSON, CSV, and arrays, and
Query caching

Version 1.5.3:
Recommended for a few minor bugfixes, and one semi-major one with include_related.

Core Changes
• Modified the way _to_object and query processing works, significantly, by merging all query processing code into one new function (_process_query).

Bug Fixes
• Fixed bug that completely broke include_required's ability to automatically add all fields.
• Fixed bugs with get_rules not being called correctly for related queries and validate->get() queries.
• Invalid relationship queries now show an error instead of silently failing.
• Fixed typo in Troubleshooting where the word 'related' was supposed to be 'required'.

Quote:Download the Latest Version Here

View the change log and the upgrade process
Having issues? Please look through the Troubleshooting Guide & FAQs
View the Complete Manual

#2
[eluser]OES[/eluser]
Fantastic work OverZealous and well done for Stensi for starting the origional project.

I have PM you OverZealous if you fell I can help.

[OES]

#3
[eluser]warrennz[/eluser]
Cool OverZealous. Have been using DMZ for sometime now and its extra functionality is awesome Smile

#4
[eluser]NachoF[/eluser]
I have decided to repost my question here cause Im pretty sure the answer to what Im looking for has to do with dmz more than datamapper

Could you help me with this query please??...
Heres my structure:

clients have many events
event has one client
events have one receipt
receipt has one event
receipts have many payments
payments have many receipts

I want to get every payment of a client in a single query… is it possible?
lets assume client id=1… I have tried many queries but I can never seem to get it done.

#5
[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.

#6
[eluser]NachoF[/eluser]
[quote author="OverZealous.com" date="1240995244"]@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.[/quote]
Ok, dont worry.... my entity relation cannot be modified... my teacher is crazy...the reasoning behind the many to many relation is that suppose a client has two pending events to be charged for... I have to give him the option to with just one payment pay those two receipts.... see?... you can pay for the event in different payments but in the end only get one receipt per event.... yet with one payment you can pay for more than one event.
Anyway, my query has been done in steps...
first get all the events of the client
then loop through them and get the receipts for each event and for each receipt loop and get the payments... its confusing but it seems to work so far....

#7
[eluser]OverZealous[/eluser]
One thing I forgot to mention that might save you a query is to use where_related() to reduce the number of queries.

Example (assumes Events has a client_id field):
Code:
// get all receipts for the customer
$receipts = new Receipt();
$receipts->where_related_event('client_id', $client->id)->select('id')->get();
$receipt_ids = new array();
foreach($receipts->all as $r) {
    $receipt_ids[] = $r->id;
}
// get all payments that belong to one of the receipts
$payments = new Payment();
$payments->where_in_related_receipt('id', $receipt_ids)->distinct()->get();

This should get all of the payments, distinctly, that are related to the client, in just 2 queries.

The nice thing about this is that you can still sort the payments list all at once.

Let me know if the above code works, since I typed it off the top of my head.

#8
[eluser]warrennz[/eluser]
Heres a tricky one

(example only - purpose is a little iffy Tongue)

User has many Invoice
Invoice has one User


I need to be able to get all the invoices, ie

Code:
$i = new Invoices();
$i->get();


But somehow order those invoices by the name field of each user.


Is something like that at all possible?

Hmm, hope thats clear.

Thanks in advance ;P

Cheers

#9
[eluser]OverZealous[/eluser]
It's easy with DMZ™!

You simply do this:
Code:
$i = new Invoices();
$i->join_related('user', array('name'));
$i->order-by('user_name');
$i->get();

Tada! :-)

#10
[eluser]NachoF[/eluser]
Im confused with join_related.. whats the difference between it and include_join_fields?


Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2017 MyBB Group.